Aave’s Oracle Issue Triggers Major Liquidations
About $27 million worth of positions were liquidated on the Aave lending platform over a 24-hour period. This wasn’t your typical market crash scenario—instead, it appears to have been triggered by a technical configuration problem with one of the protocol’s risk management systems.
Blockchain data from Chaos Labs showed the unusual spike in liquidations. Some observers initially thought it might be related to a price oracle feeding incorrect data to the protocol. Oracles are those crucial services that bring external price information onto blockchains, and lending platforms like Aave depend on them to determine when collateral values drop too low.
The Technical Breakdown
Chaos Labs later clarified what actually happened. The underlying price oracle itself was reporting correct market values. The problem was in something called the CAPO risk oracle system, which is designed to limit how quickly yield-bearing tokens like wstETH can increase in value within the protocol.
According to their explanation, there was a mismatch between stale parameters stored in a smart contract. A reference exchange rate and its associated timestamp weren’t updated in sync. This caused the CAPO system to temporarily calculate a maximum allowed exchange rate that was actually lower than wstETH’s real market value.
The effect was pretty straightforward: wstETH was treated as about 2.85% less valuable than it actually was. For borrowers using wstETH as collateral, this pushed some positions below their safety thresholds, triggering automatic liquidations.
Market Impact and Aftermath
Interestingly, trading volume for wstETH pairs remained relatively low during this period—just $10 million over 24 hours. This suggests that few traders, if any, managed to capitalize on the pricing mismatch before it corrected itself.
A Lido contributor emphasized that the issue had nothing to do with wstETH itself or the Lido protocol. “The cause has nothing to do with wstETH itself, how it works or the Lido protocol which continue to operate normally,” they told CoinDesk.
Chaos Labs noted that the protocol incurred no bad debt from the incident. However, liquidators—those traders or bots that repay risky loans in exchange for discounted collateral—captured roughly 499 ETH in liquidation bonuses and profits from the temporary price discrepancy.
Broader Context
This isn’t the first time oracle-related issues have caused problems in DeFi. Just recently, Moonwell experienced a similar situation where a misconfigured price oracle briefly valued Coinbase Wrapped ETH at about $1 instead of $2,200, leaving the protocol with nearly $1.8 million in bad debt.
What makes the Aave case different, I think, is that it wasn’t about the oracle feeding wrong prices. It was about how those prices were being processed and limited by an additional risk management layer. The system designed to prevent rapid price increases actually caused the problem by being too conservative with outdated parameters.
Aave’s spokesperson didn’t respond to requests for comment, which perhaps isn’t surprising given the technical nature of the issue. Earlier in the day, risk firm LlamaRisk had briefly posted on the AAVE forum attributing the liquidations to an issue with Chaos Labs’ risk oracle, but they deleted that post.
These incidents remind us how complex these systems have become. You’ve got multiple layers of risk management, different oracle systems, and smart contracts that need to stay perfectly synchronized. When one piece falls out of sync, even temporarily, the consequences can be significant.
The fact that no bad debt was incurred is somewhat reassuring, I suppose. It shows the system’s safety mechanisms worked in that regard. But $27 million in liquidations is still a substantial event that likely caught many users by surprise.
