Aave Liquidates $27M After Oracle Glitch: What Happened?
A technical misconfiguration has forced the Aave protocol to execute approximately $27 million in forced liquidations following a Price Oracle glitch.
The incident, which occurred due to an error in a third-party risk tool rather than a market crash, instantly seized collateral from users holding wrapped staked Ether (wstETH). This event serves as a stark reminder that Aave liquidation risks exist even when the broader market is calm, though the protocol has confirmed it will compensate affected users.
The glitch caused Aave’s system to believe that the price of wstETH had dropped significantly lower than its actual market value. Aave reported that the exchange rate applied was 2.85% below the live market rate. In the high-leverage world of DeFi, a nearly 3% discrepancy is massive. The protocol’s automated safety mechanisms kicked in immediately, incorrectly flagging healthy positions as under-collateralized and triggering a forced sell-off.
While the glitch specifically impacted wstETH positions, the vulnerability highlights the fragility of automated pricing for all assets, including peg-sensitive ones like the GHO stablecoin. The incident led to liquidators claiming about 499 ETH in profits. Fortunately for the users, Aave founder Stani Kulechov confirmed that the “configuration issue has already been remediated” and that the DAO will cover the shortfall.
— YAM
(@yieldsandmore) March 10, 2026
DISCOVER: 16+ New and Upcoming Binance Listings in 2026
For Aave Investors: Automation Has No “Undo” Button
DeFi risks are often marketed as purely market-driven. But this event proves that technical infrastructure is just as critical. Automation protects the protocol from bad debt, but when the input data is wrong, that same automation attacks its own users.
This wasn’t a malicious attack from the outside or a case of fraud, unlike the Axiom insider trading scandal where human actors allegedly manipulated systems for profit. This was a “friendly fire” incident caused by code performing exactly as it was told, based on bad instructions. It underscores that even in “blue-chip” protocols like Aave, your funds are subject to the reliability of complex, layered software dependencies.
As the industry builds frameworks for these assets, similar to the MoonPay stablecoin infrastructure recently discussed, the reliance on accurate, tamper-proof data feeds becomes the single biggest systemic risk. If the oracle fails, the smart contract fails.
Is Your DeFi Position Safe? How to Shield Your Assets
The short answer is: nothing in DeFi is 100% safe, but you can significantly reduce your risk of becoming a liquidation statistic. Crypto safety on lending platforms boils down to your Health Factor, a numeric representation of your collateral versus your debt. If you are borrowing against volatile assets, you are asking for trouble if you keep your health factor too close to the edge.
First, never treat a lending protocol as a set-it-and-forget-it savings account. You need to monitor your positions actively. If the Ethereum price experiences sudden volatility—or if an oracle glitches—a buffer is your only defense. A health factor of 1.1 might maximize your leverage, but it leaves you zero room for error. Aiming for a health factor above 2.0 provides a cushion against both market crashes and minor oracle deviations.
Second, diversify your risk. Do not keep all your spare capital in a single lending market. If a specific oracle upgrade fails on one platform, having assets elsewhere ensures you aren’t wiped out entirely. Finally, use notification tools that alert you via Telegram or email if your health factor drops. In this specific $27 million case, users had no time to react, but in most scenarios, a specialized alert gives you the critical minutes needed to add collateral and save your position.
DISCOVER: Top Rated Crypto Exchanges for 2026
Follow 99Bitcoins on X For the Latest Market Updates and Subscribe on YouTube For Daily Expert Market Analysis.
Key Takeaways
- A configuration error in an Aave risk oracle triggered $27 million in wrongful liquidations of wstETH.
- Aave has confirmed it will use DAO treasury funds and reclaimed fees to compensate all affected users.
- To protect yourself from similar glitches, maintain a high health factor buffer rather than maximizing leverage.
The post Aave Liquidates $27M After Oracle Glitch: What Happened? appeared first on 99Bitcoins.
