What is CVE-2025-61595?

CVE-2025-61595 is a high-severity uncontrolled resource consumption vulnerability in github.com/MANTRA-Chain/mantrachain/v4 (go), affecting versions < 4.0.2. It is fixed in 4.0.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which packages are affected by CVE-2025-61595?

github.com/MANTRA-Chain/mantrachain/v4 (go) versions < 4.0.2; github.com/MANTRA-Chain/mantrachain/v3 (go) versions < 4.0.2; github.com/MANTRA-Chain/mantrachain/v2 (go) versions < 4.0.2; github.com/MANTRA-Chain/mantrachain (go) versions < 4.0.2.

Is there a fix for CVE-2025-61595?

Yes. CVE-2025-61595 is fixed in 4.0.2. Upgrade to this version or later.

Is CVE-2025-61595 exploitable, and should I be worried?

Whether CVE-2025-61595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-61595 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-61595

Q: Which packages are affected by CVE-2025-61595?

github.com/MANTRA-Chain/mantrachain/v4 (go) versions < 4.0.2; github.com/MANTRA-Chain/mantrachain/v3 (go) versions < 4.0.2; github.com/MANTRA-Chain/mantrachain/v2 (go) versions < 4.0.2; github.com/MANTRA-Chain/mantrachain (go) versions < 4.0.2.

Q: Is there a fix for CVE-2025-61595?

Yes. CVE-2025-61595 is fixed in 4.0.2. Upgrade to this version or later.

Q: Is CVE-2025-61595 exploitable, and should I be worried?

Whether CVE-2025-61595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-61595 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-61595?

Upgrade github.com/MANTRA-Chain/mantrachain/v4 to 4.0.2 or later.

Summary

github.com/MANTRA-Chain/mantrachain/x/tokenfactory tx gas limit is not enforced in send hooks

It's patched in v4.0.2 and v5.0.0

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Impact

send hooks can spend more gas than what's remained in tx, combined with recursive calls in the wasm contract, can amplify the gas consumption exponentially.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

github.com/MANTRA-Chain/mantrachain/v4 (< 4.0.2) github.com/MANTRA-Chain/mantrachain/v3 (< 4.0.2) github.com/MANTRA-Chain/mantrachain/v2 (< 4.0.2) github.com/MANTRA-Chain/mantrachain (< 4.0.2)

Security releases

github.com/MANTRA-Chain/mantrachain/v4 → 4.0.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/MANTRA-Chain/mantrachain/v4 to 4.0.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-61595? CVE-2025-61595 is a high-severity uncontrolled resource consumption vulnerability in github.com/MANTRA-Chain/mantrachain/v4 (go), affecting versions < 4.0.2. It is fixed in 4.0.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which packages are affected by CVE-2025-61595?
- github.com/MANTRA-Chain/mantrachain/v4 (go) (versions < 4.0.2)
- github.com/MANTRA-Chain/mantrachain/v3 (go) (versions < 4.0.2)
- github.com/MANTRA-Chain/mantrachain/v2 (go) (versions < 4.0.2)
- github.com/MANTRA-Chain/mantrachain (go) (versions < 4.0.2)
Is there a fix for CVE-2025-61595? Yes. CVE-2025-61595 is fixed in 4.0.2. Upgrade to this version or later.
Is CVE-2025-61595 exploitable, and should I be worried? Whether CVE-2025-61595 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-61595 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-61595? Upgrade github.com/MANTRA-Chain/mantrachain/v4 to 4.0.2 or later.