Lido CSM v3 and CM v2 audit
Certora reviewed Lido (Lido CSM v3 and CM v2 audit) on 17 Mar 2026: 5 findings, 0 critical; 1 marked fixed, 4 acknowledged.
No open critical findings
Findings5
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 | 4 | 1 |
LowConsolidations create inconsistencies in CMv2 key balance accountingAcknowledged
The report gives no description here.
LowInitial deposit allocator's count-based fairness math systematically biases CMv2 stake distributionAcknowledged
The report gives no description here.
LowkeyConfirmedBalance can be stale in case of prover failure, leading to incorrect withdrawal report penalty accountingAcknowledged
The report gives no description here.
LowTop ups to validators that are in exit queue, create 2 valid withdrawal requestsAcknowledged
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 Lido’s security record
LidoAudits53 audits by 13 firmsLast audit Sep 2026, by Composable Security.
Critical findings2 criticals acknowledged, not fixedReported in 2 reports, the latest by Statemind, Apr 2023. The team acknowledged both.
Open Lido’s security recordSecurity firm
Certora9 projects reviewed · 17 reports · latest Jun 2026
See Certora’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