Securitize Bridge CCTPv2 Audit Report
Audit · firm’s term: audit report
Part of Cyfrin’s series
Cyfrin reviewed Securitize (Securitize Bridge CCTPv2 Audit Report) on 7 Oct 2025: 8 findings, 0 critical; 5 marked fixed, 3 acknowledged.
No open critical findings
Open the reportOpen Securitize’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings8
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 1 | 3 |
| Low | 0 | 2 | 2 |
MediumInvestors using smart contract wallets may have their destination chain tokens issued to an address they don’t controlAcknowledged
The report gives no description here.
LowInconsistent usage of whenNotPaused modifier for bridging fulfillment in SecuritizeBridge and USDCBridgeV2Acknowledged
The report gives no description here.
LowUpgradeable contracts which are inherited from should use ERC7201 namespaced storage layouts or storage gaps to prevent storage collisionAcknowledged
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 Securitize’s security record
SecuritizeAudits37 audits by 2 firmsLast audit Sep 2026, by Cyfrin.
Critical findingsNo open critical findingsAcross the 37 reports, 6 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Securitize’s security recordSecurity firm
Cyfrin28 projects reviewed · 79 reports · latest Sep 2026
See Cyfrin’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