A misconfigured Oracle system in Aave triggered $27 million in compelled liquidations on March 10, undervaluing wrapped staked Ether by 2.85% in opposition to its precise market fee.
In accordance with the autopsy by Chaos Labs, the CAPO oracle error brought on Aave V3 Ethereum Core and Prime situations to use an change fee of roughly 1.1939 wstETH-per-ETH when the stay onchain fee was roughly 1.228, sufficient of a spot to push 34 high-leverage E-Mode positions under their liquidation thresholds robotically.
It resulted within the liquidation of 10,938 wstETH. The protocol says it incurred no unhealthy debt and is transferring to compensate all affected customers.
The Harm: 34 Customers, $27M in Liquidations, and 499 ETH in Bot Income
The oracle glitch liquidated 34 customers, with the whole quantity reaching $27 million in wstETH positions.
Liquidation bots moved rapidly, capturing 499 ETH in bonuses, roughly $1.2 million, by executing in opposition to positions that ought to not have been eligible for liquidation at that second.
Aave founder and CEO Stani Kulechov confirmed in a Wednesday submit that the protocol generated no unhealthy debt from the incident.
1/ stETH CAPO Misconfiguration
At this time, a misconfiguration on Aave's CAPO oracle brought on wstETH E-Mode liquidations, leading to a lack of 345 ETH.
No unhealthy debt was incurred, and all affected customers might be totally reimbursed.
Extra under.— Omer Goldberg (@omeragoldberg) March 10, 2026
Of the 499 ETH that went to liquidators, Aave recaptured 141 ETH ($285,000) by way of BuilderNet refunds and an extra 13 ETH in liquidation charges.
These recovered funds will circulate on to affected customers as compensation, with DAO treasury funds masking any remaining shortfall as much as the total 345 ETH recognized as the surplus liquidation windfall.
Lido contributors confirmed the occasion had no connection to wstETH or the Lido staking protocol itself; the problem originated solely inside Aave’s oracle configuration layer.
With Ethereum value defending the $2,000 assist zone across the time of the incident, the liquidation values have been amplified by the broader market context for ETH-denominated collateral.
Uncover: The very best pre-launch crypto gross sales
Chaos Labs Confirms Aave CAPO Oracle Misconfiguration: Right here Is What They Discovered
Chaos Labs, Aave’s exterior danger administration associate, confirmed the incident stemmed from what it described as an onchain configuration misalignment beneath differing onchain replace constraints, not a design flaw within the CAPO system or within the core oracle infrastructure of Aave.
The crew emphasised that Chaos Threat Oracles had processed over 1,200 payloads and greater than 3,000 parameters throughout Aave markets with out incident previous to March 10.
Chaos Labs rapidly contained the scenario: borrow caps on wstETH have been decreased instantly, and snapshot parameters have been manually realigned to revive oracle accuracy. Kulechov famous in his public assertion that the configuration challenge had already been remediated by the point the autopsy was revealed, and praised the crew’s response velocity in limiting broader DeFi danger contagion.
The Aave governance autopsy marks this as the primary operational failure in CAPO’s deployment historical past on Aave V3, regardless of greater than a 12 months of stay operation throughout a number of markets.
What Merchants and Aave Customers Are Watching Subsequent
The quick focus is on the total reimbursement timeline. Aave DAO service suppliers are finalizing compensation for all 34 affected customers following the preliminary 141 ETH refund by way of BuilderNet, with a proper governance announcement anticipated shortly.
Past compensation, governance groups are conducting a broader evaluate of CAPO parameters throughout all Aave markets, updating stale snapshots and constructing out enhanced monitoring to flag fee divergences earlier than they attain liquidation-threshold proximity.
Whether or not that evaluate produces binding parameter replace requirements or stays advisory is the governance query to look at.
If the DAO formalizes automated CAPO sync necessities and publishes up to date danger oracle documentation, the incident might finally strengthen Aave’s operational credibility. If the evaluate stalls on the dialogue stage, the reputational price will compound the monetary one.
Discover: The best new cryptocurrencies
The submit Aave Oracle Glitch Causes $27M Liquidations: CAPO Misconfiguration Confirmed appeared first on Cryptonews.