Renzo security review
Audit · firm’s term: security review
Nethermind Security reviewed Renzo Protocol (Renzo security review) on 14 Apr 2025: 6 findings, 0 critical; 5 marked fixed, 1 acknowledged.
No open critical findings
Open the reportOpen Renzo Protocol’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings6
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 2 |
| Medium | 0 | 0 | 1 |
| Low | 0 | 1 | 2 |
Marked Info by the firm. Not counted as findings.
InfoThe fillERC20withdrawBuffer(...) function doesn’t refund excess tokens sentAcknowledged
The report gives no description here.
InfoThe totalBeaconChainExitBalance can be inflated if no checkpoint was finalized after the validator got slashedAcknowledged
The report gives no description here.
InfoThe emergencyTrackQueuedWithdrawals(...) function doesn’t verify the queued withdrawal ownership, potentially leading to inflated TVLFixed
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 Renzo Protocol’s security record
Renzo ProtocolAudits2 audits by 2 firmsLast audit Apr 2025, by Nethermind Security.
Critical findingsNo open critical findingsAcross 2 reports.
Open Renzo Protocol’s security recordSecurity firm
Nethermind Security57 projects reviewed · 81 reports · latest Sep 2026
See Nethermind Security’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