Lido V3 Oracle V7

Certora10 Dec 2025Code version: not recorded (see the report)

Audit · firm’s term: security assessment

Certora reviewed Lido (Lido V3 Oracle V7) on 10 Dec 2025: 11 findings, 0 critical; 6 marked fixed, 5 acknowledged.

No open critical findings

Open the report Open Lido’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings11

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	2
Low	0	5	2

Marked Informational by the firm. Not counted as findings.

InformationalConsensus-critical contract methods should use finalized block by defaultAcknowledged

The report gives no description here.

InformationalDivision by Zero in get_steth_by_shares FunctionAcknowledged

The report gives no description here.

InformationalOracle HTTP Provider follows HTTP Redirects (30x)Acknowledged

The report gives no description here.

Informationaloz_merkle_tree Proof Verification on Internal Node (Informational)Acknowledged

The report gives no description here.

InformationalIncorrect Events Order Leads to Wrong Fees CalculationFixed

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

Lido

Audits54 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 record

Security firm

Certora

9 projects reviewed · 17 reports · latest Jun 2026

See Certora’s audits

Something 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.