Aave V3 — CAPO Oracle Misconfiguration (System Error)

A CAPO (Correlated Asset Price Oracle) parameter update desynchronization occurred on Aave V3. The snapshotRatio parameter was rate-limited at 3% per update, but the snapshotTimestamp could advance freely without corresponding restrictions. This caused a 2.85% underpricing of wstETH. A total of 34 accounts were liquidated with $27.78M in total liquidations, but the true protocol loss was $862,000 in liquidation bonuses paid out to liquidators. The incident was classified as a system misconfiguration rather than a malicious attack.