How a 2.85% Price Error Triggered $27M in Aave Liquidations
What to Know
- $27 million in borrowing positions were liquidated on Aave on March 10, 2026 due to a brief pricing discrepancy
- The culprit was a 2.85% undervaluation of wstETH collateral — Aave's system priced it at 1.19 ETH instead of the market rate near 1.23 ETH
- Root cause traced to the CAPO risk oracle module, where outdated smart contract parameters temporarily capped wstETH's exchange rate below market value
- Liquidators extracted roughly 499 ETH in profits; Aave ended the event with zero bad debt, and governance proposed compensating affected users via DAO treasury
A 2.85% pricing error in wstETH collateral set off $27 million in Aave liquidations on March 10, 2026 — not because of a market crash, not because of a hack, but because two numbers inside a smart contract fell out of sync. The episode is a case study in how DeFi's automated machinery can turn a configuration oversight into a cascade of real financial losses.
The Day $27M Vanished in 24 Hours
Risk monitoring firm Chaos Labs was the first to flag the surge. Within a single 24-hour window on March 10, 2026, the firm identified roughly $27 million in liquidated positions across Aave markets. The size was jarring — but the cause was stranger still. No dramatic sell-off had hit the market. No exploit had drained the protocol. The trigger, once identified, turned out to be a 2.85% gap between what Aave's risk system thought wstETH was worth and what the open market was actually paying for it.
That discrepancy — barely noticeable on a price chart — was enough. Aave's algorithm briefly priced wstETH at approximately 1.19 ETH when the broader market had it sitting closer to 1.23 ETH. For borrowers who had posted wstETH as collateral, that artificial markdown made their positions look undercollateralized. The protocol's liquidation engine didn't ask questions. It did what it was designed to do.
What Is wstETH and Why Does It Matter as Collateral?
wstETH, or wrapped staked Ether, is a token issued through the Lido liquid staking protocol. When users stake ETH via Lido, they receive stETH in return — a token that reflects their staked position plus accumulated staking rewards. Because raw stETH has compatibility issues with some DeFi applications, it can be wrapped into wstETH, a static-balance token that holds the same value but works smoothly across lending markets.
The practical result: one wstETH is almost always worth more than one ETH. The excess comes from the continuous buildup of staking rewards baked into the token. That premium makes wstETH an attractive collateral choice — borrowers get to keep earning yield while using their staked ETH as backing for loans. Which is exactly why it sits at the center of billions of dollars in Aave positions.
How Do Price Oracles Work in DeFi Lending?
Why does a price oracle error matter on Aave?
Blockchains are self-contained environments — they have no native way to pull live asset prices from the outside world. Price oracles solve this by feeding real-time market data directly into smart contracts. In lending protocols like Aave, those feeds determine three things:
In normal conditions, oracles keep everything calibrated. The moment a feed goes wrong — even briefly — the downstream consequences can be severe. An artificially low collateral price shrinks a borrower's effective loan-to-value ratio. Cross the liquidation threshold and the protocol acts immediately, autonomously, and without appeal.
This is the double-edged nature of DeFi automation. The same permissionless machinery that makes it trustless and efficient is also what makes a two-percent pricing glitch financially devastating for the users caught on the wrong side of it.
- Collateral valuation — how much a deposited asset is worth in the system
- Loan health — whether a position still meets safety thresholds
- Liquidation triggers — when automated bots can legally repay debt and seize collateral
The CAPO Misconfiguration That Started It All
Deeper investigation by Chaos Labs cleared Aave's primary price oracle. It was functioning normally throughout the event. The actual fault sat one layer deeper — inside the CAPO risk oracle module, which stands for correlated assets price oracle.
CAPO is a protective layer added on top of standard oracle feeds for yield-bearing assets like wstETH. Its purpose is sensible: cap how fast the protocol accepts upward price movements, guarding against sudden manipulation or oracle exploits. Think of it as a speed limiter on how quickly an asset's value can "officially" rise within Aave's risk system.
The problem was in how that cap was calculated. CAPO references two internal parameters — a reference exchange rate and a timestamp tied to that rate. When those two values fall out of sync, the module computes an artificially low ceiling on the allowable exchange rate. Chaos Labs confirmed that exactly this happened: outdated parameters had not been refreshed together, and the resulting cap sat below wstETH's actual market price. The protocol then accepted this lower figure as truth — and liquidated accordingly.
There was no impact to the Aave Protocol.
— Stani Kulechov, Aave Founder
What Happened After Positions Were Liquidated?
Once borrowing positions crossed their safety thresholds — as computed by the misconfigured CAPO system — liquidation bots moved in fast. These are high-frequency programs built specifically to repay portions of a borrower's debt in exchange for the underlying collateral, which they acquire at a protocol-mandated discount. Across the event, liquidators collectively extracted around 499 ETH in profits and liquidation bonuses.
Importantly, Aave's core mechanisms held. The protocol ended the event with zero bad debt — every liquidated position was fully covered, and the protocol itself remained solvent. Aave founder Stani Kulechov confirmed that from the protocol's perspective, the system behaved as designed once positions breached their thresholds. The damage was real for affected borrowers. For Aave the protocol? Functionally contained.
Governance did not stop there. Aave's decentralized autonomous organization subsequently proposed compensating affected users, with refunds to be funded through a combination of recovered liquidation proceeds and DAO treasury support. It's a meaningful shift in how DeFi protocols think about technical incidents — increasingly treating oracle misconfigurations as systemic infrastructure failures rather than individual user misfortune.
Is This a wstETH Problem or an Aave Problem?
Short answer: neither, really — though that framing is a bit too clean. Contributors from the Lido side made clear that wstETH itself functioned normally throughout the incident. The token's value was accurately reflected in the open market; Lido's staking protocol was unaffected. The issue was entirely on the processing side — specifically, how Aave's CAPO module interpreted and capped incoming exchange rate data.
This isn't the first time yield-bearing token oracles have caused chaos. A separate incident on another platform saw Coinbase's wrapped staked ETH — cbETH — temporarily priced at roughly $1 instead of its actual value near $2,200, triggering its own wave of disruption. These aren't fringe edge cases anymore. They're a recurring challenge that comes with the territory of building automated financial systems around assets whose value evolves continuously over time.
As DeFi protocols take on more yield-bearing collateral, the risk models have to keep up. That means handling dynamic exchange rates, continuous staking reward accrual, and precise synchronization of smart contract parameters — all in real time. The Aave event shows what happens when even one of those pieces falls a few weeks behind schedule. You can read more about past Aave incidents to see how this pattern has played out before.
DeFi's automation is its greatest strength — and its most unforgiving characteristic. When everything syncs correctly, it works better than any bank. When parameters drift, borrowers find out the hard way.
There's a version of this story where the headline is "Aave's safety system worked perfectly" — and that's technically true. There's also a version where $27 million in real user money evaporated because a smart contract variable hadn't been updated. Both are accurate. Pick whichever one makes you more comfortable with DeFi collateral risk.
Frequently Asked Questions
What caused the $27 million in Aave liquidations on March 10, 2026?
A misconfiguration in Aave's CAPO risk oracle module caused wstETH collateral to be undervalued by approximately 2.85%. The module's reference exchange rate and timestamp parameters had fallen out of sync, creating a temporary cap on wstETH's allowable value that sat below market price, triggering automated liquidations.
What is the CAPO risk oracle on Aave?
CAPO — correlated assets price oracle — is a protective module Aave uses on top of standard price feeds for yield-bearing assets like wstETH. It caps how quickly an asset's value can rise in the system, guarding against rapid price manipulation or oracle exploits. A misconfiguration in its parameters caused the March 2026 liquidation event.
Did Aave lose money from the liquidation event?
No. Aave ended the event with zero bad debt and the protocol remained fully solvent. Aave founder Stani Kulechov confirmed the protocol was unaffected. Affected borrowers bore individual losses, but Aave governance subsequently proposed compensating them using DAO treasury funds.
What is wstETH and why is it used as DeFi collateral?
wstETH is wrapped staked Ether issued through Lido's liquid staking protocol. It represents a user's staked ETH plus accumulated staking rewards in a DeFi-compatible token. Because one wstETH is typically worth more than one ETH and earns yield passively, it is widely used as collateral in lending markets like Aave.
This article is for informational purposes only and does not constitute investment advice. Every investment and trading decision involves risk. Readers should conduct their own research before making any financial decisions.
Topics
Aave liquidationswstETH price errorCAPO risk oracleDeFi liquidationsoracle misconfigurationwstETH collateralAave governanceMilan Torres
Senior Analyst
Milan covers Bitcoin markets, macro trends, and institutional crypto adoption with a focus on data-driven analysis.
Latest Crypto News
Top Stories
Stay ahead of the market.
Crypto news and analysis delivered every morning. Free.
More from TheCryptoWorld
About the Author
Contributor
TheCryptoWorld Staff is a contributor at TheCryptoWorld.
View all contributors
Follow thecryptoworld.io on Google News to receive the latest news about blockchain, crypto, and web3.
Follow us on Google News
