Cosmos Interchain Security audit

Oak SecurityCode version: not recorded (see the report)

Oak Security reviewed Cosmos (Cosmos Interchain Security audit) on 23 Jun 2023: 11 findings, 2 critical; 4 marked fixed, 7 acknowledged.

2 critical findings, fixed
Open the reportOpen Cosmos’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings11

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical002
High002
Medium000
Low070
LowConsumer chains can DOS the provider chain by sending slash packetsAcknowledged

The report gives no description here.

LowConsumer chains can expand provider chain unbonding periodAcknowledged

The report gives no description here.

LowLastTransmissionBlockHeight is wrongly updated if the IBC token transfer failsAcknowledged

The report gives no description here.

LowPotential loss of rewards during consumer chain removalAcknowledged

The report gives no description here.

LowUnbounded loop over proposals in BeginBlock could slow down block productionAcknowledged

The report gives no description here.

LowUnbounded loops over consumer chains in EndBlock could slow down block productionAcknowledged

The report gives no description here.

LowValidators can evade slashing if an equivocation proposal is submitted seven days or later after the infractionAcknowledged

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 Cosmos’s security record

Cosmos
Audits2 audits by 2 firmsLast audit Jun 2023, by Oak Security.
Critical findingsNo open critical findingsAcross the 2 reports, 2 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Cosmos’s security record

Security firm

Oak Security

33 projects reviewed · 60 reports · latest May 2026

See Oak Security’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.

Tell us