How severe is GHSA-6jrf-4jv4-r9mw?

No CVSS score has been assigned to GHSA-6jrf-4jv4-r9mw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6jrf-4jv4-r9mw?

GHSA-6jrf-4jv4-r9mw affects the following packages: tendermint-light-client-verifier (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-6jrf-4jv4-r9mw?

Update tendermint-light-client-verifier to 0.40.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jrf-4jv4-r9mw is resolved across your whole dependency graph.

How do I detect GHSA-6jrf-4jv4-r9mw in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tendermint-light-client-verifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6jrf-4jv4-r9mw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6jrf-4jv4-r9mw actively exploited in the wild?

No public exploit code has been indexed for GHSA-6jrf-4jv4-r9mw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6jrf-4jv4-r9mw published, and has it been updated?

GHSA-6jrf-4jv4-r9mw was published on April 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

tendermint-rs's Light Client Verifier allows malicious validators to spoof votes from other validatorsGHSA-6jrf-4jv4-r9mw

Fix: informalsystems/tendermint-rs@1aabcfe

GHSA-6jrf-4jv4-r9mw is a security vulnerability in tendermint-light-client-verifier. A fix is available for tendermint-light-client-verifier — see the affected versions and patch details below.

Published

Apr 9, 2025

Updated

Apr 9, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 9, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀tendermint-light-client-verifier

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Name: ISA-2025-003: Malicious validator can spoof votes from other validators Component: tendermint-rs Criticality: High (Catastrophic Impact; Rare Likelihood per ACMv1.2) Affected versions: <= v0.40.2 Affected users: Everyone

Description

tendermint-rs contains a critical vulnerability in its light client implementation due to insecure handling of corrupted validator sets. Because it doesn't check that the validator address is correctly derived from the validator's public key when counting votes, it is possible to spoof votes from other validators. The result is being able to construct the malicious block and cheat the light client. The light client will accept such a block, seemingly signed by 2/3+ majority.

Patches

The new tendermint-rs release v0.40.3 fixes this issue.

Unreleased code in the main branch is patched as well.

Workarounds

There are no known workarounds for this issue.

Timeline

March 12, 2025, 13:41pm PST: Issue reported
March 12, 2025, 03:00am PST: Core team completes validation of issue

This issue was reported by Felix Wilhelm from Asymmetric Research.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tendermint-light-client-verifier`	all versions	0.40.3`cargo update -p tendermint-light-client-verifier --precise 0.40.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tendermint-light-client-verifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tendermint-light-client-verifier to 0.40.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jrf-4jv4-r9mw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Name: ISA-2025-003: Malicious validator can spoof votes from other validators Component: tendermint-rs Criticality: High (Catastrophic Impact; Rare Likelihood per [ACMv1.2](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md)) Affected versions: <= v0.40.2 Affected users: Everyone ### Description tendermint-rs contains a critical vulnerability in its light client implementation due to insecure handling of corrupted validator sets. Because it doesn't check that the validator address is correctly derived from the validator's public key when counting votes, it

O3 Security · Impact-Aware SCA

Is GHSA-6jrf-4jv4-r9mw in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works