zkSync

OpenZeppelin8 Mar 2023Files named in the report

Part of OpenZeppelin’s series

OpenZeppelin reviewed ZKsync on 8 Mar 2023: 13 findings, 0 critical; 6 marked fixed, 4 acknowledged, 3 open.

No open critical findings

Open the report Open ZKsync’s security record

Report hosted on blog.openzeppelin.com.

Trustblock does not review code.

Findings13

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	1	1
Medium	3	0	3
Low	0	3	2

HighETH withdrawal within allowed limit could failFixed

The report gives no description here.

MediumRefund recipient defaults to inaccessible address for contractsFixed

The report gives no description here.

MediumUnchecked subtraction underflowFixed

The report gives no description here.

MediumUser could deposit more ETH than allowedFixed

The report gives no description here.

LowL2 transaction hash is not emittedFixed

The report gives no description here.

LowMissing documentationFixed

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.

Repository and files the report names (13)

IGovernance.sol
L2ContractHelper.sol
Allowlist.sol
DiamondInit.sol
Storage.sol
IAllowList.sol
AddressAliasHelper.sol
Getters.sol
Config.sol
IGetters.sol
IMailbox.sol
Mailbox.sol
Governance.sol

Part of ZKsync’s security record

ZKsync

Audits18 audits by 1 firmLast audit Feb 2025, by OpenZeppelin.

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

Open ZKsync’s security record

Security firm

OpenZeppelin

67 projects reviewed · 184 reports · latest Aug 2026

See OpenZeppelin’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.