Aave Oracle Glitch Leads to $27 Million in Liquidations: Misconfiguration Confirmed

On March 10, a misconfigured Oracle system in Aave resulted in $27 million in forced liquidations due to an undervaluation of wrapped staked Ether. This incident was confirmed by a post-mortem conducted by Chaos Labs, highlighting how a mistake in the CAPO oracle led to significant financial consequences for some users.

Key Takeaways

Aave experienced $27 million in forced liquidations due to an oracle misconfiguration.
34 users were affected, with liquidation bots profiting by capturing 499 ETH.
Aave confirmed it incurred no bad debt and is working on compensating all affected users.
Chaos Labs identified the misalignment in on-chain configuration, not a flaw in the oracle system itself.
Aave is taking measures to prevent future occurrences and ensure better monitoring.

Aave Oracle Glitch Causes $27M Liquidations — CAPO Misconfiguration Confirmed

The Incident: $27 Million in Liquidations

A misconfigured Oracle system in Aave caused over $27 million in forced liquidations on March 10. This was due to a 2.85% undervaluation of wrapped staked Ether (wstETH) compared to its actual market rate.

According to Chaos Labs, which conducted a post-mortem analysis, the CAPO oracle error caused Aave's V3 Ethereum Core and Prime instances to apply an exchange rate of about 1.1939 wstETH per ETH, while the actual on-chain rate was approximately 1.228. This discrepancy was significant enough to automatically push 34 high-leverage E-Mode positions below their liquidation thresholds.

This glitch led to the liquidation of 10,938 wstETH, but Aave reported that it did not incur any bad debt and is committed to compensating all impacted users.

The Impact: 34 Users Affected and Profits for Liquidators

The oracle error liquidated 34 users, amounting to a total of $27 million in wstETH liquidation. Liquidation bots acted swiftly, capturing 499 ETH in profits, which is roughly $1.2 million, from positions that were not supposed to be liquidated at that moment.

Aave's founder and CEO, Stani Kulechov, confirmed that the protocol did not generate any bad debt from this incident. Out of the 499 ETH obtained by liquidators, Aave managed to recover 141 ETH (valued at $285,000) through BuilderNet refunds, along with an additional 13 ETH in liquidation fees.

The recovered funds will be distributed to affected users as compensation, with the DAO treasury covering any shortfall, up to the total of 345 ETH identified as excess liquidation profits.

Lido contributors also clarified that the incident was not related to wstETH or the Lido staking protocol; the issue was entirely due to Aave’s oracle configuration.

With Ethereum maintaining a support zone around $2,000 during the incident, the liquidation amounts were further influenced by the overall market environment for ETH-denominated collateral.

Aave Oracle Glitch Causes $27M Liquidations — CAPO Misconfiguration Confirmed

Findings: Chaos Labs Confirms CAPO Oracle Misconfiguration

Chaos Labs, Aave’s external risk management partner, confirmed that the underlying issue was an on-chain configuration misalignment rather than a design flaw in the CAPO system or Aave’s core oracle infrastructure. The team stressed that prior to March 10, the Chaos Risk Oracles had processed over 1,200 transactions and more than 3,000 parameters without any issues.

They quickly contained the situation by reducing borrow caps on wstETH and manually realigning snapshot parameters to ensure accurate oracle readings. Kulechov noted in his public statement that the configuration issue had already been resolved by the time the post-mortem was published and commended the team for acting promptly to limit wider risks within the DeFi space.

This incident marks the first operational failure in the CAPO system’s deployment history on Aave V3, even though it had been functioning across several markets for over a year.

Next Steps for Traders and Aave Users

The immediate concern for Aave users is the timeline for full reimbursements. Service providers from Aave DAO are working on compensating all 34 affected users following the initial 141 ETH refund via BuilderNet, with a formal announcement from the governance expected soon.

In addition to compensation, the governance teams are reviewing CAPO parameters across all Aave markets. They are focusing on updating outdated snapshots and developing improved monitoring systems to detect rate divergences before they approach liquidation thresholds.

A key governance question remains whether this review will lead to binding parameter updates or merely serve as advisory recommendations. Should the DAO formalize new automated CAPO synchronization requirements and publish updated risk oracle documentation, the incident could ultimately reinforce Aave’s operational credibility. Conversely, if the review process stalls, the reputational damage may compound the financial losses experienced.