Router Protocol security record

Arbitrum, Avalanche, BNB Chain, Ethereum, Fantom, Optimism, Polygon (POS)routerprotocol.comXGitHub

As of 21 Oct 2026, Router Protocol has 2 audit reports by 1 security firm on Trustblock; the latest is by Oak Security, dated 29 May 2024. Those reports list no open critical findings.

Critical findings
No open critical findings
Across the 2 reports, 8 critical findings were reported. Each is marked fixed by the firm that reported it. See the findings
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.

Audits2

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Router Integration auditSecurity firm: Oak SecurityDate: Scope: Not recorded (see the report)1 critical finding, fixedOpen · GitHub
Router Chain 2 auditSecurity firm: Oak SecurityDate: Scope: Not recorded (see the report)7 critical findings, fixedOpen · GitHub

Findings32

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

SeverityOpenAcknowledgedFixed
Critical008
High0014
Medium000
Low028
CriticalFailed cross-chain requests are repeatedly processed in Router Chain’s EndBlocker, potentially causing Denial-of-ServiceRouter Integration audit · Oak Security · 29 May 2024Fixed

The report gives no description here.

Open the report
CriticalAnyone can submit forged cross-chain ack requestsRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
CriticalAnyone can submit forged cross-chain requestsRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
CriticalBlocked cross-chain requests are indefinitely retried and could be exploited for denial-of-service attacksRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
CriticalDeactivated price feeders are not enforcedRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
CriticalNon-deterministic iteration in ClaimEventSlashing can cause consensus failureRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
CriticalUnapproved fee payers can block legitimate requests which can be exploited for denial-of-service attacksRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
CriticalUnbonding validators can circumvent slashingRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighFee settlement can be bypassed for inbound and crosstalk requests, resulting in relayers not being compensatedRouter Integration audit · Oak Security · 29 May 2024Fixed

The report gives no description here.

Open the report
HighMalicious relayer can purposefully fail cross-chain requests on EVM destination chainsRouter Integration audit · Oak Security · 29 May 2024Fixed

The report gives no description here.

Open the report
Show 10 more
HighNEAR gateway contract does not allocate sufficient gas for handler callsRouter Integration audit · Oak Security · 29 May 2024Fixed

The report gives no description here.

Open the report
HighAnyone can create a new relayer configuration with a potentially invalid IBC channel, resulting in failed cross-chain requests via IBCRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighCustom application panics in EndBlocker can halt the chainRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighExecuting crosstalk requests with a missing IBC relayer config results in indefinite retries and liveness issuesRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighFailed cross-chain ack requests are incorrectly stored as successfulRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighFailed requests will not be reflected for ErrorGasOverflow panicsRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighGetLastUnBondingBlockHeight will always return zeroRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighIncomplete genesis handling causes loss of storage valuesRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighSlashing risk due to sequential attestation processingRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighSymbol prices requested by the BandChain oracle are not namespaced by the price feeder name, resulting in the inability to retrieve pricesRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
Show 10 more
HighUnhandled errors in the codebaseRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
HighZero values initialization affects gas handling and fee refundsRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
LowAmino codec must be registered to support end users with hardware devices like LedgerRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
LowErrors are not propagated correctlyRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
Lowgas-prices and token-prices CLI commands are ineffective due to not specifying the PriceFeederName and corresponding pricesRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
LowHandleAckDefaultValidation does not update the event block height, causing incorrect query responses to be returnedRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
LowPrice feeders can feed prices with older resolve timesRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
Lowrwasm module does not support InstantiateContract2, UpdateAdmin, and ClearAdminRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
LowThe execute-cw-contract CLI command does not supply Msg and Funds to the MsgExecuteContract messageRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report
LowValidators joining the network after attestations were submitted are subject to slashing and have to attest to previous claimsRouter Chain 2 audit · Oak Security · 30 Apr 2024Fixed

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="router-protocol"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

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