Uniswap v4 core audit

Trail of Bits5 Sep 2024Code version: not recorded (see the report)

Audit · firm’s term: security assessment

Trail of Bits reviewed Uniswap (Uniswap v4 core audit) on 5 Sep 2024: 1 finding, 0 critical; it is marked fixed.

No open critical findings

Open the report Open Uniswap’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings1

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	0
Low	0	0	1

Marked Informational by the firm. Not counted as findings.

InformationalSimilar-looking pool IDs can be brute forced through the PoolKey hooks fieldsOpen

The report gives no description here.

InformationalIncorrect variable usage on swap feeFixed

The report gives no description here.

InformationalInsufficient event generation PartiallyFixed

The report gives no description here.

InformationalStrict equality on fee comparison can lead the fees to be greater than 100%Fixed

The report gives no description here.

InformationalUse of incorrect mask to clear higher bits of the protocolFee valueFixed

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 Uniswap’s security record

Uniswap

Audits16 audits by 5 firmsLast audit Aug 2026, by Cantina.

Critical findingsNo open critical findingsAcross the 16 reports, 7 critical findings were reported. Each is marked fixed by the firm that reported it.

IncidentIncident 17 Apr 2020Source: De.Fi incident database.

Open Uniswap’s security record

Security firm

Trail of Bits

7 projects reviewed · 7 reports · latest Jan 2025

See Trail of Bits’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.