Aave Oracle Glitch Triggers $26M in Unfair wstETH Liquidations
Aave's Ethereum Core and Prime instances suffered a CAPO misconfiguration on March 10, 2026, causing $26-27 million in erroneous wstETH liquidations affecting 34 accounts.
- 01The glitch undervalued wstETH by 2.85%, triggering liquidations for 34 accounts on March 10, 2026.
- 02Liquidators earned 499 ETH in bonuses, while the Aave DAO plans to use up to 345 ETH from its treasury to supplement the 141.5 ETH already recovered for user reimbursement.
- 03The incident was caused by a 3% growth cap on the 'snapshotRatio' parameter that prevented it from reaching the required 1.2282 value in a single update.
What Happened
Aave experienced a critical pricing glitch on March 10, 2026, that triggered approximately $26 million to $27 million in unfair liquidations of wrapped staked ETH (wstETH) positions The Block. The AAVE token trades at $111.40 as of March 11, 2026, while ETH stands at $2,020.
The incident affected 34 accounts across Aave's Ethereum Core and Prime instances, with roughly 10,938 wstETH liquidated at undervalued prices The Block. Third-party liquidators captured approximately 499 ETH in profits from the event, equivalent to roughly $1 million at current prices CoinDesk.
Aave's Risk Stewards recovered 141.5 ETH for compensation as of March 11, 2026, with the DAO considering additional treasury funds to reimburse affected users Chaos Labs. The protocol did not accrue any bad debt from the incident.
Background
The glitch originated from a misconfiguration in Aave's Correlated Asset Price Oracle (CAPO), which manages pricing for correlated assets like wstETH and ETH Chaos Labs. An on-chain constraint limited the 'snapshotRatio' update to 3% growth every 3 days, causing misalignment with the 'snapshotTimestamp' parameter.
This configuration error resulted in wstETH being undervalued by approximately 2.85% as of March 10, 2026. The protocol reported a price of ~1.1939 ETH while the actual market rate stood at ~1.228 ETH Chaos Labs. The 3% growth cap prevented the snapshotRatio from reaching the required 1.2282 value in a single update cycle.
CAPO was designed to improve capital efficiency for correlated assets by allowing higher loan-to-value ratios while maintaining safety through price correlation tracking. This incident marks one of the largest oracle-related liquidation events in DeFi lending history.
The Bull Case
Chaos Labs, Aave's primary risk steward, stated the incident was not a flaw in the underlying CAPO design but rather a configuration misalignment Chaos Labs. The security firm confirmed the protocol has already been reverted to its prior safe configuration.
Aave Governance demonstrated quick intervention through its emergency response mechanisms. The recovery of 141.5 ETH for compensation within 24 hours shows the protocol's commitment to user protection and operational resilience. Risk Stewards identified the issue, halted affected markets, and initiated recovery procedures without external coordination delays.
The fact that Aave accrued zero bad debt despite $26 million in erroneous liquidations indicates the protocol's overall risk management framework remained intact. Only the oracle pricing layer failed, not the core lending mechanics or collateral management systems.
The Bear Case
LlamaRisk, a competing risk management firm, initially attributed the liquidations to an issue with the risk oracle itself, highlighting concerns over the transparency and complexity of delegated risk parameters CoinDesk. The firm noted that users cannot easily verify oracle configurations before depositing funds.
Market observers on Reddit and social media expressed concern that 'healthy' positions were liquidated due to internal protocol logic rather than actual market conditions The Block. This undermines the 'safe' reputation of E-Mode for yield-bearing assets, which was marketed as providing extra protection for correlated collateral pairs.
Critics argue that a 3% update cap on critical price parameters creates unnecessary single points of failure. If oracle updates cannot reflect market reality within a reasonable timeframe, the system prioritizes administrative constraints over accurate price discovery.
What to Watch
Affected users should monitor Aave Governance proposals for compensation distribution timelines. The DAO must approve treasury fund allocation beyond the 141.5 ETH already recovered. Aave's March 15, 2026 governance call will likely address reimbursement procedures.
Track CAPO parameter changes across other correlated asset pairs. USDe, sETH, and other liquid staking tokens remain on Aave with similar oracle configurations. Any additional misconfigurations could trigger cascading liquidations.
Monitor liquidator behavior for potential exploitation patterns. The 499 ETH in profits may incentivize actors to probe for similar oracle weaknesses across DeFi protocols. Competing lending platforms may see increased scrutiny of their oracle implementations.
Watch AAVE token price action for market confidence signals. A sustained drop below $100 could indicate reduced trust in the protocol's risk management. Current price stands at $111.40 as of March 11, 2026.