Lido Vault Middleware Audit Report
Audit · firm’s term: audit report
Cyfrin reviewed Lido (Lido Vault Middleware Audit Report) on 19 Dec 2025: 5 findings, 0 critical; all marked fixed.
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 | 0 | 5 |
Marked Informational or Gas by the firm. Not counted as findings.
InformationalNot including _decimalsOffset when calculating the fee sharesAcknowledged
The report gives no description here.
InformationalEmergencyVault::activateRecovery NatSpec references wrong event nameFixed
The report gives no description here.
InformationalIn Solidity don’t initialize to default valuesFixed
The report gives no description here.
InformationalnonReentrant is not the first modifierFixed
The report gives no description here.
GasUse more efficient method of reading recipient account and basis pointsFixed
The report gives no description here.
InformationalUse named mappings to explicitly denote the purpose of keys and valuesFixed
The report gives no description here.
GasUse ReentrancyGuardTransient for faster nonReentrant modifiersFixed
The report gives no description here.
InformationalVault::decimals does not reflect correct decimals when OFFSET is usedFixed
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
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