Written by: Cointelegraph

Translated by: AididiaoJP, Foresight News

Key Points Summary

• A temporary pricing deviation of 2.85% for wstETH collateral triggered approximately $27 million in liquidations on Aave. This event demonstrates that even minor technical issues can lead to significant financial impacts in automated DeFi lending systems.
• The wave of liquidations occurred because the Aave system briefly assessed the value of wstETH at about 1.19 ETH, while the market value at the time was close to 1.23 ETH, resulting in some loan positions being mistakenly judged as under-collateralized.
• Price oracles are key infrastructure in DeFi, responsible for transmitting external market data to smart contracts to determine collateral value, assess loan health, and trigger automatic liquidations.
• The root of the problem was not a failure of the price data source but rather improper configuration of Aave's CAPO risk oracle module. Outdated smart contract parameters within the module set a temporary cap on token exchange rates.

DeFi protocols rely on automated logic to handle everything from collateral management to risk assessment. While this mechanism establishes a truly open and permissionless financial system, it also means that minor technical issues can quickly escalate, causing severe financial turmoil.

According to the risk monitoring agency Chaos Labs, a market downturn on March 10, 2026, triggered approximately $27 million in liquidations of borrower positions on Aave, clearly illustrating this vulnerability. Within 24 hours, user positions worth about $27 million were liquidated. Surprisingly, this event was not caused by large-scale market sell-offs but rather by a temporary 2.85% price deviation in wrapped staked ETH (wstETH) collateral.

This event serves as a strong reminder that the reliability of price oracles and sound risk management frameworks are crucial to maintaining the stability of the DeFi ecosystem.

This article explains how the 2.85% pricing deviation of wstETH collateral triggered around $27 million in liquidations on the Aave lending protocol. It focuses on analyzing how oracle configuration, smart contract parameters, and automatic liquidation mechanisms amplify small pricing errors in the DeFi market.

Sudden Surge of Liquidations

When a wave of liquidations struck the Aave market, Chaos Labs, which closely monitors abnormal activities in lending protocols, quickly identified and reported the situation. Initially, market observers speculated that a failure of the price oracle had resulted in collateral assets on the platform being mispriced.

Price oracles play a crucial bridging role, providing external market prices to on-chain applications. In lending protocols like Aave, this price data directly determines whether a borrower's collateral is sufficient to cover their loan. Once the collateral value falls below the required safety threshold, the system automatically liquidates the position.

The core asset in this incident was wstETH, a token widely used as collateral in the DeFi lending ecosystem.

Liquidation speeds on lending protocols like Aave typically far exceed traditional margin calls. The DeFi market operates 24/7 through automated smart contracts, so once the collateralization ratio falls below the stipulated threshold, positions may be liquidated in seconds.

What is wstETH?

wstETH (wrapped staked Ether) is a token issued by the liquid staking protocol Lido.

When users stake Ether through Lido, they first receive stETH, which represents their staked ETH principal and accumulated staking rewards. To enhance compatibility with various DeFi applications, stETH can be "wrapped" into wstETH.

Due to the continuous accumulation of staking rewards, the value of 1 wstETH is typically slightly above 1 ETH. This characteristic makes it an attractive and widely used type of collateral in the DeFi lending market.

Pricing Deviation Event

During this wave of liquidations, a discrepancy emerged between the actual market value of wstETH and the valuation adopted by Aave's risk system. Aave's algorithm priced wstETH at approximately 1.19 ETH, while the broader market valuation at the time was around 1.23 ETH.

The about 2.85% valuation difference made the under-collateralization of positions backed by wstETH appear more severe than it actually was.

As a result, some borrower positions fell below the necessary safety threshold, triggering Aave's automatic liquidation process.

Why Price Oracles are Crucial in DeFi

Price oracles are the underlying infrastructure of DeFi. Since blockchains themselves cannot obtain real-world market data, they must rely on oracle services to provide external price information for assets. This price data directly affects:

• Valuation of collateral
• Health of loan positions
• Decisions to trigger liquidations

Once the price of collateral reports a decline, the protocol may deem loan collateral insufficient, thus automatically liquidating the relevant positions.

Since this mechanism is entirely algorithm-driven, even small pricing deviations can trigger severe chain reactions.

In the DeFi space, small price deviations can also have huge impacts. Temporary fluctuations in oracle prices or market prices, even by just a few percentage points, can trigger chain liquidations. This risk is particularly pronounced when many borrowers use high-leverage positions and volatile cryptocurrencies as collateral.

The True Cause: CAPO Risk Oracle Misconfiguration

In-depth investigations confirmed that Aave's main price oracle was functioning normally.

The problem actually lay with the "Collateral Asset Price Oracle" (CAPO) risk module, which serves as a protective layer for specific assets.

The primary function of CAPO is to set a rate cap for the value increase of yield-bearing tokens like wstETH, aiming to mitigate the risks of sudden price surges or potential oracle attacks.

However, in this incident, inconsistencies in the configuration within the CAPO module led to the problem.

Technical Error Analysis

Chaos Labs revealed that the issue stemmed from outdated parameters stored in the smart contract.

Two key parameters failed to sync updates:

• Reference exchange rate
• Timestamp associated with that exchange rate

Because these two parameters were not synchronized, the allowable exchange rate cap calculated by CAPO was set lower than the actual market rate at that time.

This led to the protocol undervaluing wstETH by about 2.85% compared to the market price.

Aave relies on price oracles, which provide real-time asset price data to smart contracts. If these data sources briefly reflect anomalous market prices from exchanges, the protocol will automatically recompute the collateral value and may trigger liquidations.

The Chain Reaction of Liquidations

Once the collateralization ratio falls below the safety threshold, Aave's automatic liquidation engine is immediately triggered.

Liquidators (usually high-speed trading bots) quickly intervene, repaying part of the borrower's debt to obtain corresponding collateral at a preset discount price.

In this incident, approximately $27 million worth of borrower positions were liquidated.

Liquidators profited approximately 499 ETH from this brief price dislocation (including liquidation bonuses).

No Bad Debt Generated by the Protocol Itself

Despite the large scale of liquidations, the Aave protocol itself did not generate any bad debt. Aave founder Stani Kulechov stated, "There was no impact on the Aave protocol."

Chaos Labs pointed out that once positions broke through the safety threshold, the platform's core risk control and liquidation mechanisms functioned normally as designed. Therefore, the impact of this incident was limited to the relevant borrowers and did not threaten the overall solvency and stability of the Aave protocol. It was indeed the temporary artificial suppression of collateral value that caused some borrowing positions to drop below the liquidation line.

The Aave governance layer subsequently proposed to compensate affected users by utilizing recovered funds and the decentralized autonomous organization (DAO) treasury. This approach reflects a new trend in DeFi governance: protocols are beginning to view such technical incidents as systemic infrastructure risks and are inclined to compensate affected users rather than placing the entire burden of loss on them.

A Renewed Warning on DeFi Oracle Risks

This event highlights that the design of oracle mechanisms is not only one of the most critical components of DeFi infrastructure but also one of its most vulnerable points.

When automated mechanisms manage billions of dollars in collateral value, even minor configuration errors can lead to consequences far beyond expectations.

Similar events have occurred on other DeFi platforms. For example, one platform briefly valued Coinbase's wrapped staked ETH (cbETH) at about $1 (its actual value was around $2,200) due to an oracle configuration error, causing widespread chaos.

These cases illustrate that in a decentralized financial system, maintaining reliable and accurate price data sources remains a continuous challenge.

wstETH and Lido Are Not At Fault

Relevantly, contributors to the Lido ecosystem have made it clear that this liquidation was not caused by any faults or defects of the wstETH token itself.

The token operated normally throughout the entire event, and the underlying Lido staking protocol remained fully available and unaffected.

The core of the problem lies within Aave's lending protocol, which, through its own risk management configuration, produced a discrepancy in how it handled and interpreted price data.

Insights for the Future Development of DeFi

As decentralized finance continues to develop, various protocols are deploying increasingly sophisticated risk management systems to accommodate yield-bearing assets like wstETH.

These assets present unique pricing challenges as their value continues to rise with the accumulation of staking rewards.

Therefore, effective risk models must adequately manage the following factors:

• Dynamic exchange rates
• Continuously accumulating staking rewards
• Time-dependent parameter updates
• Precise synchronization of smart contract parameters

Even minor discrepancies between these factors can escalate into large-scale liquidation events.