Price glitch triggers $27M DeFi liquidations

TLDR

Aaves lending protocol saw about $27 million of loans liquidated after a temporary pricing error in its wstETH oracle.

1. A misconfigured CAPO risk oracle undervalued wstETH by about 2.85 percent, making otherwise safe positions look undercollateralized and triggering automated liquidations around $27 million.
2. Roughly 34 accounts lost collateral while bots captured about 499 ETH in bonuses, but Aave remained solvent and the DAO plus partners have moved to fully reimburse affected users.
3. The event highlights oracle configuration risk in DeFi and is driving governance changes and monitoring upgrades that users should watch as a signal of how robust Aave remains.

Deep Dive

1. How The Glitch Caused $27M Liquidations

Reports agree that a configuration error in Aaves CAPO risk oracle briefly mispriced wstETH, a yield bearing Lido staked ETH derivative, against ETH.

Instead of tracking the live market ratio, the oracle used a stale snapshot, valuing wstETH at about 1.19 ETH while markets were closer to 1.23 ETH, an underpricing of roughly 2.85 percent. This made leveraged wstETH collateral look weaker than it really was, so several positions crossed liquidation thresholds and about 10,938 wstETH, worth roughly $27 million, was liquidated in a short window.

Coverage from CoinDesk and others describes this as an internal risk oracle configuration issue, not a hack or a broad market crash, with the underlying price feed still reflecting real market values.

2. Who Was Hit And How Aave Responded

Around 34 user accounts using wstETH as collateral were liquidated, while liquidation bots earned about 499 ETH in incentives and arbitrage profits from the mispricing.

Crucially, the protocol itself did not incur bad debt, and Aaves core markets stayed solvent throughout the incident. Aaves team, Chaos Labs, and Lido contributors have stated that affected users will be reimbursed using recovered funds plus Aave DAO treasury resources, with governance proposals already in motion to formalize compensation.

This combination of no protocol insolvency plus active reimbursement is important: the operational failure hurt specific users with tight leverage, but it did not threaten Aaves survival.

3. DeFi Risk Lessons And What To Watch

The episode underlines that oracle and configuration risk is just as real as smart contract bugs or price crashes in DeFi. Even a small valuation error, applied system wide, can liquidate healthy positions.

Aaves governance and risk teams are reviewing CAPO parameters, adding tighter monitoring, and considering stricter standards for how and when oracle configs can change. Similar incidents at other protocols have already pushed the ecosystem toward more conservative oracle designs.

Conclusion

A single oracle configuration mistake on Aave turned into roughly $27 million of forced liquidations, even though markets themselves were stable. The protocol stayed solvent and plans to make users whole, but the incident is a clear reminder that operational risk in DeFi can be sudden and mechanical, and that governance and oracle practices are key signals to watch when assessing platform safety.