Aave V4 Hub
Formal verification · firm’s term: formal verification report · Includes formal verification
Certora reviewed Aave (Aave V4 Hub) on 9 Mar 2026: 6 findings, 0 critical; all marked fixed.
No open critical findings
Findings6
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 3 |
| Low | 0 | 0 | 3 |
MediumShare rate decreases due to rounding error in fee calculationFixed
The report gives no description here.
MediumShare rate decreases to less than one due to rounding error in totalAssetsFixed
The report gives no description here.
MediumSpoke accounting can be broken if addSpoke() is called on an existing spokeFixed
The report gives no description here.
LowArbitrary transferFrom parameters can break protocol solvencyFixed
The report gives no description here.
LowLoss of assets due to a missing update to drawn indexFixed
The report gives no description here.
LowView functions don’t take into account the accrued feesFixed
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Part of Aave’s security record
AaveAudits36 audits by 14 firmsLast audit Jun 2026, by Certora.
Critical findingsNo open critical findingsAcross the 36 reports, 8 critical findings were reported. Each is marked fixed by the firm that reported it.
IncidentIncident 27 Aug 2024Source: De.Fi incident database.
Open Aave’s security recordSecurity firm
Certora29 projects reviewed · 56 reports · latest Aug 2026
See Certora’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us