Lido Csm V2
Ackee Blockchain Security reviewed Lido (Lido Csm V2) on 16 Sep 2025: 6 findings, 0 critical; all marked fixed.
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 | 0 | 3 |
Marked Warning or Info by the firm. Not counted as findings.
InfoUnused codeOpen
The report gives no description here.
WarningDepositable validators count can be updated on non-existing node operatorsAcknowledged
The report gives no description here.
WarningDuplicate getSigningKeys call in processBadPerformanceProofAcknowledged
The report gives no description here.
InfoLido and StETH ambiguous namingAcknowledged
The report gives no description here.
Warning_validateKeyNumberValueInte rvals in CSParametersRegistry does not check for empty arraysFixed
The report gives no description here.
WarningDivision by zero in processBadPerformanceProofFixed
The report gives no description here.
InfoInconsistent unchecked use in CSBondCurveFixed
The report gives no description here.
WarningInvalid tagging of memory-safe assemblyFixed
The report gives no description here.
WarningNode operator creation transient flag not clearedFixed
The report gives no description here.
WarningNode operators can self-referFixed
The report gives no description here.
Show 4 more
WarningsubmitWithdrawals griefingFixed
The report gives no description here.
InfoTyposFixed
The report gives no description here.
WarningUnconditional emission of ReferralRecorded eventFixed
The report gives no description here.
WarningValidatorWithdrawalInfo struct contains unused isSlashed fieldFixed
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
LidoSecurity firm
Ackee Blockchain Security39 projects reviewed · 81 reports · latest Jul 2026
See Ackee Blockchain 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