What Happened During the Aave Oracle Malfunction?
A temporary oracle malfunction on the Aave protocol triggered roughly $26 million in liquidations after a pricing discrepancy affected positions tied to wrapped staked Ether (wstETH). The incident occurred on March 10 across Aave’s Ethereum Core and Prime markets, according to a post-mortem published by Chaos Labs, the protocol’s primary risk management provider.
The issue was traced to a misconfiguration within Aave’s Correlated Asset Price Oracle (CAPO), a mechanism designed to prevent sudden price spikes or drops in correlated assets. Because of a mismatch in the oracle parameters, the system briefly reported a capped exchange rate far below the prevailing market level.
Chaos Labs said the oracle produced an exchange rate of about 1.1939 while the actual market rate was near 1.228. That discrepancy triggered automated liquidations in Aave’s E-Mode markets, where users can borrow against highly correlated collateral with tighter risk thresholds.
The event affected 34 accounts and led to the liquidation of roughly 10,938 wstETH. The total value of positions liquidated under the incorrect pricing conditions was estimated at around $26 million.
Investor Takeaway
Why Did the Oracle Produce the Wrong Price?
According to the Chaos Labs post-mortem, the malfunction stemmed from a mismatch between two parameters used by CAPO: the snapshot ratio and the snapshot timestamp. These values help determine the capped exchange rate used to protect markets from sudden valuation swings.
The issue arose when an offchain process attempted to update the snapshot ratio to reflect the correct historical exchange rate. However, the protocol includes an onchain rule that limits how quickly this parameter can be adjusted.
“Operationally, our offchain process determined that the snapshot ratio should be updated to approximately ~1.2282, the appropriate value corresponding to the exchange rate 7 days earlier,” the report said. “However, the snapshot ratio parameter is subject to an onchain constraint: it can only be increased by 3% every 3 days … It was not possible to set it to ~1.2282 in a single update.”
Because of that restriction, the update produced a temporary mismatch between the snapshot ratio and timestamp values. Chaos Labs said the discrepancy resulted in a 2.85% drop in the effective exchange rate used by the protocol, enough to trigger liquidations under Aave’s collateral thresholds.
Who Benefited From the Liquidations?
While affected borrowers lost collateral during the incident, third-party liquidators profited from the pricing mismatch. According to the post-mortem, liquidators earned around 499 ETH in gains from the forced liquidations triggered during the oracle glitch.
Despite the liquidations, the protocol itself did not accumulate bad debt. That distinction matters because DeFi lending systems can face solvency risks when collateral is liquidated below outstanding loan balances.
In this case, the losses were borne by individual borrowers rather than the protocol’s reserve system. However, the scale of the event drew attention because the liquidations were triggered by a configuration mismatch rather than market volatility.
Investor Takeaway
How Aave Is Addressing the Incident
Chaos Labs said it acted quickly to stabilize the system after the issue was detected. The team temporarily reduced wstETH borrow caps and manually aligned the snapshot parameters so the oracle would reflect the correct exchange rate.
A compensation plan for affected users is now underway. According to the report, 141.5 ETH recovered from the incident will be used as part of the reimbursement process, with an additional allocation of up to 345 ETH from the Aave DAO treasury if required.
Chaos Labs said the problem did not stem from a flaw in the CAPO design itself but from a configuration mismatch during parameter updates.
“Ultimately, this incident did not reflect a flaw in the underlying CAPO or offchain risk oracle design, but rather an onchain configuration misalignment under differing onchain update constraints that led the snapshot ratio and snapshot timestamp to become misaligned,” the report said.
The incident highlights a persistent challenge in decentralized finance: even well-tested protocols remain dependent on precise coordination between offchain processes and onchain rules.
