Aave V3 audit

Sigma PrimeCode version: not recorded (see the report)

Sigma Prime reviewed Aave (Aave V3 audit) on 27 Jan 2022: 3 findings, 0 critical; all marked fixed.

No open critical findings
Open the reportOpen Aave’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings3

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low003

Marked Informational by the firm. Not counted as findings.

InformationalConfigurator Decimals Are Parameters Rather than FetchedAcknowledged

The report gives no description here.

InformationalEvent MintUnbacked Field user is Always Set to BridgeAcknowledged

The report gives no description here.

InformationalGas Optimisation - Reduce Ternary OperatorsFixed

The report gives no description here.

InformationalMiscellaneous General CommentsFixed

The report gives no description here.

InformationalNo Getter For _stableRateExcessOffsetFixed

The report gives no description here.

InformationalRepeated Arguments Passed in validateRebalanceStableBorrowRate()Fixed

The report gives no description here.

InformationalUnnecessary Storage Reads When Fetch DebtFixed

The report gives no description here.

InformationalUnused Struct Variables and ErrorsFixed

The report gives no description here.

InformationalVerification POOL Matches the ConfiguratorFixed

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

Aave
Audits28 audits by 11 firmsLast audit Jun 2026, by Certora.
Critical findingsNo open critical findingsAcross the 28 reports, 6 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 record

Security firm

Sigma Prime

16 projects reviewed · 37 reports · latest Aug 2026

See Sigma Prime’s audits

Something 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