Aave V3.8 went live across active Aave V3 markets on 15 chains, according to a November 12, 2026 report. Approved by Aave DAO and developed by Aave Labs, the upgrade adds a reentrancy guard to the lending pool’s core contracts for operations involving external callbacks.
The rollout includes Ethereum’s Core and Lido instances, as well as active instances on Plasma, Avalanche, BNB Chain, Monad, Base, Arbitrum, Mantle, X Layer, Polygon, Linea, Optimism, Gnosis, MegaETH and Celo. Frozen legacy markets with limits set to zero were excluded. DeFiLlama data cited in the report put Aave’s total value locked above $16.4 billion as of November 12, with more than $15.23 billion in active V3 markets.

How the guard works
V3.8 uses EIP-1153 transient storage for its lock. Unlike persistent storage, transient storage clears at the end of a transaction. The report says its TSTORE and TLOAD operations each cost 100 gas, avoiding the higher cost of maintaining a persistent lock.
The guard is deliberately asymmetric. Aave Labs said the flashLoan and flashLoanSimple entry points check whether a lock is active but do not set one themselves. That allows a flash-loan callback to include a liquidation, deposit or repayment. A flash-loan request made during a callback from an ordinary pool operation, however, is blocked and reverts.
Aave Labs posted the governance-forum proposal on October 21, followed by a Snapshot vote on October 27 and the AIP #541 on-chain vote beginning November 9. The report says Certora formal verification and an independent external security audit were completed before the AIP vote, and the updated contracts were published in Aave V3’s official repository under a Business Source License.
The guard does not remove every integration concern. Community developers cautioned that an external protocol reading pool view functions during a callback—such as an account health factor or reserve data—may encounter an intermediate accounting state. Downstream integrations still need to account for that boundary.


