CVE-2025-61595 — v4
Fix: MANTRA-Chain/mantrachain@30d36c4CVE-2025-61595 is a Uncontrolled Resource Consumption vulnerability in github.com/MANTRA-Chain/mantrachain/v4. A fix is available for github.com/MANTRA-Chain/mantrachain/v4 — see the affected versions and patch details below.
MANTRA tx gas limit is not enforced in send hooks
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-61595.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/MANTRA-Chain/mantrachain/v4🐹github.com/MANTRA-Chain/mantrachain/v3🐹github.com/MANTRA-Chain/mantrachain/v2🐹github.com/MANTRA-Chain/mantrachainReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/MANTRA-Chain/mantrachain/v4 | all versions | 4.0.2go get github.com/MANTRA-Chain/mantrachain/v4@v4.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 dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/MANTRA-Chain/mantrachain/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-61595 can be triaged on real exposure rather than presence alone.
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
Is CVE-2025-61595 in your dependencies?
O3 Security finds CVE-2025-61595 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.