Key conclusions

• A transient 2.85% price divergence in wstETH collateral resulted in approximately $27 million worth of Aave liquidation, showing that even minor technical issues can have major financial consequences in automated DeFi lending systems.

• The liquidation wave occurred because the Aave system briefly valued wstETH at around 1.19 ETH instead of its market value around 1.23 ETH, making some of the loan positions appear under-collateralized.

• Price oracles are a critical infrastructure in DeFi because they provide external market data to astute contracts, determining the value of collateral, the health of loans, and when automatic liquidation should occur.

• The root cause was not an erroneous price feed, but a misconfiguration in Aave’s CAPO risk Oracle system, where antiquated astute contract parameters resulted in a transient cap on the token’s exchange rate.

Decentralized finance (DeFi) protocols employ automated logic to handle everything from security management to risk assessment. While this setup enables a truly open and permissionless financial system, it also means that minor technical issues can snowball into significant financial disruptions.

According to risk monitoring firm Chaos Labs, the market downturn that occurred on March 10, 2026 resulted in approximately $27 million in Aave borrower liquidations, clearly illustrating this gap. Approximately $27 million worth of user positions were liquidated in one 24-hour window. Surprisingly, this was not due to a massive market sell-off but rather a tiny price divergence of 2.85% that impacted the wrapped security ETH (wstETH).

This event is a stark reminder of how critical price oracles and a solid risk management framework are to the stability of the DeFi ecosystem.

A sudden enhance in the number of liquidations

When the liquidation wave occurred in Aave markets, Chaos Labs, which tracks lending protocols for unusual activity, quickly identified and flagged this enhance. Early speculation among observers pointed to a possible failure of price oracles, which could result in the mispricing of underlying assets on the platform.

Price oracles serve as critical bridges, providing market prices to onchain applications. In lending protocols like Aave, these channels determine whether a borrower’s collateral is still sufficient to cover his or her loan. When the value of the collateral falls below the required threshold, the system triggers automatic liquidation of the position.

The asset at the center of this event was wstETH, a token commonly used as collateral in DeFi lending ecosystems.

Did you know? Liquidations for lending protocols like Aave often occur faster than time-honored margin calls. Since DeFi markets operate 24/7 via automated astute contracts, positions can be liquidated in seconds when collateralization ratios fall below required thresholds.

What is wstETH?

wstETH, or Wrapped Stacked Ether (ETH), is a token issued via the Lido protocol, the leading liquid staking protocol.

When users stake Ether via Lido, they initially receive stETH, which represents their staked ETH and accrued staking rewards. To improve compatibility with various DeFi applications, stETH can be wrapped in wstETH.

Due to the continuous accumulation of staking rewards, one wstETH is usually worth slightly more than one ETH. This makes it a particularly attractive and widely adopted form of collateral in DeFi lending markets.

Price discrepancy

During the liquidation wave, a discrepancy emerged between the actual market value of wstETH and the valuation used in the Aave risk system. Aave’s algorithm valued wstETH at around 1.19 ETH, while the broader market priced it closer to 1.23 ETH.

This difference of approximately 2.85% caused positions hedged by wstETH to appear more under-hedged than they actually were.

As a result, some loan positions fell below the required safety thresholds, triggering Aave’s automatic liquidation process.

Why price oracles are critical in DeFi

Price oracles are vital infrastructure in DeFi. Blockchains cannot natively pull real-world market data, so Oracle Services provides external sources of asset prices. These channels directly influence:

A reported decline in the price of the collateral may result in the protocol deeming the loan insufficiently collateralized, resulting in automatic liquidation of the position.

Because this mechanism works algorithmically, even tiny price deviations can have stern consequences.

Did you know? A tiny price discrepancy can have huge effects in DeFi. Even a brief deviation in the market or oracle price by just a few percent can result in cascading liquidations. This is especially true when multiple borrowers are using highly leveraged positions backed by floating crypto collateral.

Real cause: CAPO-Oracle risk misconfiguration

Deeper analysis confirmed that Aave’s main price oracle was functioning normally.

Instead, the main concern was the Correlated Asset Price Risk (CAPO) Oracle module, which provided an additional layer of protection applied to select assets.

CAPO is specifically designed to limit the rate of enhance in the value of profit tokens such as wstETH. This safeguard helps protect the protocol against price spikes or potential Oracle exploits.

However, in this case the problem was caused by configuration inconsistency in CAPO.

Technical description of the error

Chaos Labs revealed that the fault was caused by antiquated parameters stored in the astute contract.

Two key values ​​fell out of alignment:

Because they were not refreshed in tandem, CAPO calculated a transient ceiling on the allowable exchange rate that was below the prevailing market value.

This caused the protocol to undervalue wstETH by approximately 2.85% from its prevailing market price.

Did you know? Aave relies on price oracles, i.e. data sources that provide real-time asset prices to astute contracts. If this data briefly reflects abnormal market prices from exchanges, the protocol automatically recalculates collateral values ​​and may result in liquidation.

Liquidation cascade

As soon as the collateralization ratios fell below the required thresholds, Aave’s automatic liquidation mechanism was triggered.

Liquidators, typically quick-trading bots, stepped in, paying off some of the borrower’s debt and in return purchasing the underlying security at a built-in discount.

Approximately $27 million worth of debt items were eliminated throughout this event.

The liquidators ultimately extracted approximately 499 ETH in combined profits and liquidation bonuses by taking advantage of the short-term price divergence.

The protocol does not create any bad debts

Even with liquidation volume, Aave remained at zero debt. Founder of Aave Stani Kulechov he stated that “it had no impact on the Aave protocol.”

Chaos Labs concluded that the platform’s underlying risk and liquidation mechanisms operated as designed when positions exceeded their thresholds. If items exceeded safety thresholds, liquidation proceeded as planned.

The disruption was therefore restricted to the individual borrowers affected and did not threaten the overall solvency or stability of the protocol. The resulting artificial reduction in the value of the collateral pushed several borrowed positions below the liquidation thresholds.

Aave management proposed compensating affected users phrases financed by recovered funds and fiscal support from a decentralized autonomous organization (DAO). This approach is consistent with the changing governance pattern of DeFi, where protocols increasingly view technical incidents as a risk to system infrastructure. They can move to compensate affected users rather than leaving them with constant losses.

Oracle risk reminder in DeFi

The event highlights that the Oracle project remains one of the most significant and sensitive pieces of DeFi infrastructure.

Even tiny configuration errors can have huge consequences when automated mechanisms oversee billions of dollars in collateral value.

Comparable episodes have occurred on other DeFi platforms. For example: incorrectly configured Oracle temporarily priced Coinbase’s wrapped ETH (cbETH) at around $1 instead of around $2,200, sparking widespread disruption.

Such cases highlight the ongoing challenges of maintaining reliable and precise price data in decentralized financial systems.

wstETH and Lido were not responsible

Collaborators in the Lido ecosystem have made it clear that the liquidations were not for any reason malfunction or an error in wstETH itself.

The token operated normally throughout the event and the underlying Lido staking protocol remained fully functional and intact.

The main problem appeared to stem from the way the Aave lending protocol processed and interpreted pricing data within its own risk management setup.

Lessons for the future of DeFi

As decentralized finance continues to evolve, protocols include increasingly sophisticated risk management systems to accommodate income-producing assets such as wstETH.

These assets pose unique pricing challenges because their value continually increases over time by accumulating staking rewards.

Effective risk models must therefore adequately handle:

Even tiny discrepancies in these elements can turn into mass liquidation.