Securitize Audit Report
Audit · firm’s term: audit report
Part of Cyfrin’s series
Cyfrin reviewed Securitize (Securitize Audit Report) on 17 Dec 2024: 9 findings, 1 critical; 8 marked fixed, 1 acknowledged.
Report hosted on GitHub.
Trustblock does not review code.
Findings9
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 3 |
| Low | 0 | 1 | 4 |
CriticalSecuritizeVault’s share token is in wrong decimalsFixed
The report gives no description here.
MediumAmbiguous owner terminology creates confusion in access control of SecuritizeVaultFixed
The report gives no description here.
MediumInconsistent token amount in external redemption process of Securitize- Vault’s liquidate functionFixed
The report gives no description here.
MediumLack of slippage protection in the SecuritizeVault’s liquidation functionFixed
The report gives no description here.
LowInsufficient storage gap in BaseSecuritizeSwap contractFixed
The report gives no description here.
LowMissing input validation in privileged functionsFixed
The report gives no description here.
LowMissing PausableUpgradable initialization in SecuritizeSwap contract initializationFixed
The report gives no description here.
LowPotential replay attacks due to static DOMAINS EP ARAT ORFixed
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
SecuritizeSecurity 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