What Happened in the Aave Oracle Incident? $26M Liquidations Explained

A configuration error in a price oracle used by Aave triggered roughly $26–27 million in liquidations on Tuesday, after the system temporarily undervalued a key ethereum staking asset used as collateral.

DeFi Lending Giant Aave Moves to Reimburse Users After Oracle Mispricing

The issue involved Aave’s Correlated Asset Price Oracle (CAPO), which is designed to cap price movements for closely related assets. During the incident, the oracle briefly reported the exchange rate for wrapped staked ether (wstETH) at about 1.1939 instead of the actual market level near 1.228, a gap of roughly 2.85%.

That discrepancy proved large enough to trigger automatic liquidations in Aave V3’s Efficiency Mode, known as E-Mode, where highly correlated assets can be borrowed against each other with higher loan-to-value ratios. In this case, leveraged positions backed by wstETH slipped below the required health threshold.

Blockchain data and protocol analysis show that about 10,938 wstETH across 34 accounts were liquidated during the event. At prevailing prices, the transactions represented roughly $26–27 million in collateral movements across Aave’s Ethereum Core and Prime deployments.

Liquidators captured approximately 499 ether in total value from the event. That figure includes about 116 ether in liquidation bonuses and fees, along with roughly 382 ether tied to the pricing discrepancy that temporarily undervalued the collateral.

Despite the sharp liquidations, the protocol itself did not incur bad debt. Aave’s liquidation system functioned as designed, meaning the platform remained solvent even as the oracle input briefly mispriced the asset.

The affected collateral is tied to Lido Finance, whose wrapped staking token steadily increases in value relative to ether as staking rewards accumulate. Lido confirmed the incident was unrelated to its staking infrastructure and instead stemmed from Aave’s internal oracle configuration.

According to technical analysis from risk partner Chaos Labs, the root cause involved a mismatch between timestamp updates and price-ratio limits within CAPO’s smart-contract constraints.

The oracle contract enforces a cap on how quickly the snapshot ratio can increase—limited to about 3% every three days—to protect against manipulation attacks. When the offchain oracle attempted to update the exchange rate using a seven-day reference window, the contract restricted the ratio increase while still updating the timestamp.

That mismatch caused the system to calculate an artificially low maximum exchange rate for wstETH, creating the temporary undervaluation that pushed some leveraged accounts into liquidation territory.

The problem was identified and resolved within hours. Risk stewards manually aligned the snapshot ratio with the updated timestamp window, restoring the oracle’s effective price range to match the live market rate.

As a precaution, Aave temporarily reduced the borrow cap for wstETH to one token on both its Core and Prime instances, preventing new leverage from forming while engineers verified the fix.

The protocol also recovered part of the liquidation proceeds. About 141.5 ether was recaptured through BuilderNet refunds tied to the oracle update, along with roughly 13 ether in associated fees.

Aave founder Stani Kulechov said the incident represented only about 0.00274% of the protocol’s overall scale and emphasized that the core system remained intact.

“A reimbursement plan is currently being coordinated by Service Providers (SPs) to compensate affected borrowers using fees previously earned from liquidations,” Kulechov wrote on X.

“Every affected user will be fully reimbursed,” Chaos Labs founder Omer Goldberg said in an update, noting that recovered funds will be used first and any remaining compensation—capped at roughly 345 ether—will come from the Aave DAO treasury.

DAO special-purpose entities are finalizing the reimbursement mechanism, with a formal proposal expected shortly.

While contained, the event highlights how configuration errors—rather than outright hacks—can still ripple through DeFi systems that rely on complex oracle logic and highly leveraged lending markets.

The episode also illustrates a defining trait of modern DeFi infrastructure: even when a glitch forces millions in liquidations, the protocol can remain solvent, recover funds, and reimburse users without halting operations.

FAQ 🔎

• What caused the Aave liquidation event on March 10, 2026?

A configuration mismatch in Aave’s CAPO oracle temporarily undervalued wstETH collateral by about 2.85%, triggering automated liquidations.

• How much value was liquidated in the Aave oracle incident?

Approximately 10,938 wstETH across 34 accounts—worth roughly $26–27 million—were liquidated.

• Did Aave suffer losses or bad debt from the event?

No, the protocol remained solvent and incurred zero bad debt.

• Will affected Aave users be reimbursed?

Yes, Aave DAO plans to compensate all impacted users using recovered funds and treasury reserves.