What happened on March 10, 2026
In a single day of trading chaos, a misconfiguration in Aave's CAPO oracle fed the V3 Ethereum Core and Prime deployments with an out‑of‑sync price for wstETH relative to ETH. The resulting undervaluation of roughly 2.85% triggered a wave of automated liquidations among high‑leverage users.
The CAPO feed priced wstETH at about 1.1939 ETH per wstETH, while live on‑chain markets showed a rate near 1.228 ETH per wstETH. That gap pushed 34 elevated E‑Mode positions below their liquidation thresholds, unleashing roughly $27 million in wstETH liquidations across the protocol.
How the CAPO misconfiguration unfolded
The error emerged from the CAPO oracle configuration layer and affected Aave's own feeds, not the underlying wstETH contracts or Lido’s staking mechanism. The mispricing set off a cascade in the protocol’s risk checks, causing automatic liquidations of positions that appeared healthy only moments earlier.
Overall, the event culminated in the liquidation of 10,938 wstETH. Bots accelerated the process, capturing 499 ETH in liquidation bonuses during the frenzy. The episode was not a breach, but a mispriced feed incident that exposed how quickly DeFi can swing when an oracle feed diverges from market reality.
Aave’s response and compensation plan
Stani Kulechov, founder and CEO of AAVE, stated in a public post that the protocol incurred no bad debt from the incident and that all affected users will be fully reimbursed. He added that the project remains committed to backstopping losses through treasury funds if needed to achieve complete compensation.
Chaos Labs’ post‑mortem quantified the scope: 34 affected users, $27 million in liquidations, and 499 ETH captured by bots. On the recovery side, 141 ETH, valued at about $285,000, was refunded through BuilderNet, and 13 ETH in liquidation fees was also reclaimed. The Aave DAO treasury has pledged to cover any remaining shortfall up to the identified windfall of 345 ETH.
Market context and risk implications
The incident lands amid a volatile stretch for Ethereum in March 2026, with ETH hovering near the $2,000 level. The episode underscores how aave oracle glitch causes real‑world risk for lenders that rely on external price feeds and risk models. It also spotlights the fragility of oracle ecosystems when mispricing aligns with aggressive leverage, potentially triggering cascading liquidations across multiple protocols.
Analysts say the event should accelerate discussions around cross‑protocol oracle resilience, faster remediation processes, and more robust guardrails to detect mispricing before liquidations escalate. It also serves as a reminder to traders that even established DeFi platforms can be exposed to feed errors that look minor in isolation but become material when leverage is high.
What’s next for Aave and its users
Aave has committed to patching CAPO’s pricing logic and expanding monitoring and redundancy to prevent a repeat. The protocol is implementing a structured reimbursement workflow and coordinating with the DAO to ensure all affected users are made whole, with treasury funds ready to cover any shortfall.
Industry watchers say this incident may set a precedent for stricter controls around oracle configuration, including more frequent sanity checks and automated cross‑verification against on‑chain prices. The DeFi ecosystem continues to push for stronger, more transparent risk management as liquidity providers and borrowers weigh the reliability of price feeds in volatile markets.
Key data points from the event
- 34 affected users
- $27 million in liquidations (wstETH positions)
- 10,938 wstETH liquidated
- 499 ETH captured by liquidation bots
- 141 ETH recovered through BuilderNet refunds (≈$285,000)
- 13 ETH recovered in liquidation fees
- 345 ETH identified as excess liquidation windfall
- No bad debt incurred
Bottom line for the crypto market
The event demonstrates the persistent risk from oracle reliance in DeFi and how aave oracle glitch causes a ripple effect across users and liquidity providers. While reimbursed losses soften the impact, risk management teams will likely tighten their controls, and users will watch closely for how quickly Aave and other protocols can shore up price feeds against future mispricing events.
Discussion