Aave is working to compensate users after a configuration problem in its correlated-asset price oracle pushed the protocol into using an incorrect wstETH exchange rate, triggering roughly $26 million in liquidations that should not have happened under the correct price.

The clearest root-source account comes from a March 10 post-mortem by Chaos Labs on the Aave governance forum, where the risk provider said a technical incident affecting the CAPO risk oracle caused the reported wstETH/stETH exchange-rate cap to fall below the valid market rate on Aave’s Ethereum Core and Prime instances.

According to that write-up, the incident produced an approximately 2.85% downward deviation in the effective exchange rate used by the protocol and triggered about 10,938 wstETH in E-Mode liquidations across 34 accounts. Chaos Labs said the protocol did not incur bad debt, but users were still improperly liquidated and will be compensated through recovered liquidation revenue and, if needed, Aave DAO treasury funds.

What Went Wrong

The issue was not a market crash or a sudden dislocation in wstETH itself. It was an internal mismatch inside the oracle guardrail system meant to protect the protocol from manipulated exchange-rate jumps.

Chaos Labs said the oracle relies on two linked reference points, a snapshot ratio and a snapshot timestamp, that are supposed to stay aligned. In this case, the snapshot ratio could only be increased gradually because of an on-chain rate limit, while the timestamp still advanced to a seven-day-old reference point as intended by the off-chain logic. That left the system calculating a maximum allowed exchange rate from a ratio that was too low for the timestamp it was using.

The result was a capped exchange rate of about 1.1939, below the correct market-reflective rate. Once that lower value fed into the protocol, some positions suddenly appeared less healthy than they really were, and the liquidation engine treated them as eligible for liquidation.

Why That Triggered Liquidations So Fast

Aave’s liquidation system reacts to collateral values and health factors, not to user intent or contextual judgment. Once the oracle reported a lower effective value for wstETH, positions near the margin were pushed below the threshold needed to stay open.

That is why the incident turned into a liquidation event so quickly. A relatively small pricing deviation can have an outsized effect in leveraged E-Mode positions because the margin for error is already tight. In this case, a roughly 2.85% artificial price move was enough to force liquidations across dozens of accounts.

The important point is that this was not the market correctly repricing risk. It was the protocol ingesting an erroneous constrained value from its own guardrail configuration.

How Aave Responded

Chaos Labs said Aave immediately reduced the wstETH borrow cap to 1 on the affected Core and Prime instances to limit additional exposure while the issue was being fixed. The team then manually realigned the snapshot ratio with the snapshot timestamp so the oracle would revert to the true exchange rate.

The protocol has since been returned to its prior price-oracle configuration, according to the post-mortem, and Chaos Labs recommended restoring the borrow caps to their original levels after the oracle was corrected.

That sequence matters because it shows the issue was treated as a contained configuration incident, not as a persistent flaw in the live market price of wstETH or a broader breakdown in Aave’s solvency. Chaos Labs explicitly said no bad debt accrued to the protocol.

How Compensation Will Work

The post-mortem says Aave recaptured 141.5 ETH in liquidation-bonus revenue through BuilderNet refunds, plus about 13 ETH in liquidation fees, and that those recovered funds will be used to partially compensate impacted users. The remaining user losses, if any, are expected to be covered through the Aave treasury under a separate compensation plan.

Chaos Labs also said no more than 345 ETH would need to be compensated on an ad hoc basis from the DAO after accounting for recovered funds and other ongoing recovery efforts. In practical terms, that means the protocol is not disputing that the liquidations were caused by the oracle incident. It is already structuring a treasury-backed path to make affected users whole.

Why the Incident Matters

This incident cuts deeper than a normal liquidation headline because it hit one of DeFi’s most sensitive trust layers, protocol-side pricing infrastructure. Oracle systems and guardrails exist to stop bad liquidations and protect lending markets from manipulated collateral values. When a protective mechanism itself becomes the source of bad pricing, the market starts looking beyond the size of the loss and toward process risk.

For Aave, the immediate damage looks manageable. There was no bad debt, the error has been contained, and compensation is on the way. But the episode still matters because it shows how even a risk-control mechanism can become part of the attack surface or failure surface when linked parameters evolve under different constraints.

That is why the market reaction is likely to focus less on whether Aave survives this event, and more on what safeguards get added next. The protocol has already framed the glitch as a configuration misalignment rather than a flaw in CAPO’s core design. The next credibility test is whether that distinction is enough to reassure users that the same kind of mismatch cannot happen again under live conditions.

The post Aave Oracle Glitch Triggers $26 Million in Improper Liquidations appeared first on Crypto Adventure.

---

Filed under: Bitcoin - @ March 11, 2026 9:28 am