$27 Million Aave Liquidation Event Sparked by Oracle Configuration Error

TLDR

• Aave experienced an oracle pricing malfunction on March 10, 2026, resulting in approximately $27 million worth of liquidations.
• The technical error affected wstETH, a liquid staking derivative from Lido, undervaluing it by roughly 2.85% compared to actual market rates.
• Approximately 34 user positions were incorrectly liquidated due to the pricing discrepancy.
• Liquidation bots and traders earned around 499 ETH from the mispricing incident.
• Risk manager Chaos Labs has verified zero bad debt occurred and guaranteed complete reimbursement for all impacted users.

On March 10, 2026, the decentralized finance protocol Aave encountered an oracle configuration problem that resulted in approximately $27 million in liquidations impacting about 34 user positions. The incident stemmed from a technical glitch in the way Aave’s system calculated the price of wstETH, Lido’s liquid staking token representing staked Ethereum.

Price oracles serve as critical infrastructure that delivers off-chain market data to on-chain protocols. For Aave, oracles monitor collateral valuations to ensure loans remain adequately backed. If collateral value drops beneath specified safety margins, the platform initiates automatic liquidation procedures.

The root cause was traced to Aave’s Correlated Asset Price Oracle (CAPO). This specialized mechanism prevents volatile price spikes by imposing limits on how rapidly yield-generating token values can appreciate.

CAPO operates using a snapshot ratio paired with a snapshot timestamp to determine the maximum permissible exchange rate. During this incident, these two critical parameters became desynchronized.

According to Chaos Labs, Aave’s lead risk management firm, an off-chain update attempted to adjust the snapshot ratio to roughly 1.2282. Unfortunately, protocol safeguards restrict this ratio from increasing more than 3% within any three-day window.

Since the full adjustment couldn’t be executed in one transaction, the snapshot ratio and timestamp became mismatched. This synchronization failure caused CAPO to output a capped exchange rate near 1.1939, significantly below the actual market rate of approximately 1.228.

The consequence was that wstETH appeared approximately 2.85% undervalued within the protocol. This artificial devaluation triggered automated liquidations for positions that would have otherwise remained healthy.

What Happened to Affected Users

The malfunction led to the liquidation of roughly 10,938 wstETH spread across 34 separate accounts. Automated liquidation systems and opportunistic traders captured approximately 499 ETH in liquidation bonuses and arbitrage profits.

Chaos Labs verified that the Aave protocol itself sustained zero bad debt from the incident. Aave Labs CEO and founder Stani Kulechov stated on X that the event had “no impact to the Aave Protocol.”

A contributor from Lido clarified to CoinDesk that the problem was entirely isolated to Aave’s oracle system and had no connection to wstETH or the Lido protocol, both of which functioned normally throughout the episode.

Compensation Plan

Chaos Labs acted swiftly by implementing emergency measures including reducing wstETH borrowing limits and manually correcting the snapshot parameters to restore accurate oracle pricing.

A comprehensive reimbursement program has been initiated. Chaos Labs reported recovering 141.5 ETH from the incident and will allocate up to 345 ETH from Aave DAO’s treasury to ensure complete compensation for affected parties.

Market data shows wstETH traded only $10 million in volume during the 24-hour period encompassing the incident, indicating limited opportunity for widespread exploitation of the pricing anomaly before correction.

The post $27 Million Aave Liquidation Event Sparked by Oracle Configuration Error appeared first on Blockonomi.