Aave V3.8 adds reentrancy protection across active V3 markets

As reported on November 12, 2026, Aave V3.8 had gone live following Aave DAO approval. Developed by Aave Labs, the upgrade adds pool-level reentrancy protection for external callbacks. Aave’s announcement said the deployment covered active instances on 15 chains; 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. Those figures describe assets deposited in the protocol, not an assessment of its security.

What changed in the callback path

V3.8 uses EIP-1153 transient storage for its reentrancy lock. Unlike a persistent storage lock, the transient state clears at the end of a transaction. The report says TSTORE and TLOAD each cost 100 gas, limiting the overhead of the protection.

The lock is asymmetric. According to Aave Labs, flashLoan and flashLoanSimple check whether the pool is locked but do not themselves set the lock. A flash-loan callback can therefore still combine actions such as liquidation, deposit or repayment. A flash-loan request made during the callback of a regular pool operation, however, is blocked and reverted.

Aave V3.8 adds reentrancy protection across active V3 markets

Deployment and remaining boundary

Aave Labs posted the governance-forum proposal on October 21, submitted it to Snapshot on October 27, and opened the AIP #541 on-chain vote on November 9. The report says Certora formal verification and an independent external security audit were completed before the AIP vote. The updated contracts were published in the official Aave V3 repository under a Business Source License.

Community developers also cautioned integrators that pool view functions—including account health-factor and reserve-data reads—may expose intermediate ledger state during an external callback. The new lock does not remove that integration risk.