Aave V2 is a mature but aging lending protocol. Its legacy status means declining liquidity, lower security priority, and now reduced governance coverage following the ACI/BGD Labs exit. Users with remaining V2 positions should actively plan migration to V3 to access better risk parameters and deeper liquidity.
Risk Breakdown
Top Risks
Aave V2 is a legacy deployment with active migration to V3/V4. Governance attention and security patches prioritize newer versions, leaving V2 with slower response times to emerging threats — worsened by the March 2026 exit of ACI (61% of governance actions) and BGD Labs from the DAO.
November 2023 security incident affected V2 markets across multiple chains, requiring emergency asset freezes. While no funds were lost, the vulnerability pattern demonstrates V2's aging codebase risk.
At $136M remaining TVL, V2 still holds substantial user funds in deprecated markets where interest rate models and risk parameters receive less frequent governance updates — with V4 launch focus consuming remaining DAO capacity.
Frequently Asked Questions
Is Aave V2 safe to use?
What are the main risks of using Aave V2?
What is Aave V2's risk score breakdown?
How does Aave V2 compare to other Lending protocols?
Has Aave V2 ever been hacked or exploited?
Get risk alerts before it's too late
Weekly grade changes, downgrade alerts, and new protocol risk findings. Free.