How severe is CVE-2025-61595?

No CVSS score has been assigned to CVE-2025-61595 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-61595?

CVE-2025-61595 affects the following packages: github.com/MANTRA-Chain/mantrachain/v4 (Go), github.com/MANTRA-Chain/mantrachain/v3 (Go), github.com/MANTRA-Chain/mantrachain/v2 (Go), github.com/MANTRA-Chain/mantrachain (Go). Ecosystems affected: Go.

How do I fix CVE-2025-61595?

Update github.com/MANTRA-Chain/mantrachain/v4 to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-61595 is resolved across your whole dependency graph.

How do I detect CVE-2025-61595 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/MANTRA-Chain/mantrachain/v4. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-61595 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.

How does O3 Security protect against CVE-2025-61595?

O3 pinpoints whether CVE-2025-61595 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-61595 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-61595 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.

What type of vulnerability is CVE-2025-61595?

CVE-2025-61595 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-61595 published, and has it been updated?

CVE-2025-61595 was published on October 2, 2025 and was last updated on July 31, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-61595

Fix: MANTRA-Chain/mantrachain@30d36c4

CVE-2025-61595 is a Uncontrolled Resource Consumption vulnerability in github.com/MANTRA-Chain/mantrachain/v4. O3 Security confirms whether CVE-2025-61595 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MANTRA tx gas limit is not enforced in send hooks

Also known asGHSA-qwvm-wqq8-8j69GO-2025-3997

Published

Oct 2, 2025

Updated

Jul 31, 2026

Affected

4 pkgs

Patched

1 / 4

Exploits

None indexed

Exploitation data as of Jul 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

🐹github.com/MANTRA-Chain/mantrachain/v4🐹github.com/MANTRA-Chain/mantrachain/v3🐹github.com/MANTRA-Chain/mantrachain/v2🐹github.com/MANTRA-Chain/mantrachain

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

Description

MANTRA is a purpose-built RWA Layer 1 Blockchain, capable of adherence to real world regulatory requirements. Versions 4.0.1 and below do not enforce the tx gas limit in its send hooks. Send hooks can spend more gas than what remains in tx, combined with recursive calls in the wasm contract, potentially amplifying the gas consumption exponentially. This is fixed in version 4.0.2.

Affected Packages

4 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/MANTRA-Chain/mantrachain/v4`	all versions	4.0.2
🐹Go	`github.com/MANTRA-Chain/mantrachain/v3`	all versions	No fix
🐹Go	`github.com/MANTRA-Chain/mantrachain/v2`	all versions	No fix
🐹Go	`github.com/MANTRA-Chain/mantrachain`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/MANTRA-Chain/mantrachain/v4. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/MANTRA-Chain/mantrachain/v4 to 4.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-61595 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.
How O3 protects you
O3 pinpoints whether CVE-2025-61595 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-61595. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-61595 in your dependencies?

O3 detects CVE-2025-61595 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works