Summary
Namada-apps can Crash with Excessive Computation in Mempool Validation
Workarounds
There are no workarounds and users are advised to upgrade.
Impact
A malicious transaction may cause a crash in mempool validation.
A transaction with authorization section containing 256 public keys or more with valid matching signatures triggers an integer overflow in signature verification that causes a the node to panic.
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
This issue has been patched in apps version 1.1.0. The mempool validation has been fixed to avoid overflow.
Frequently Asked Questions
- What is GHSA-82VG-5V4F-F9WQ? GHSA-82VG-5V4F-F9WQ is a critical-severity allocation of resources without limits or throttling vulnerability in namada-apps (rust), affecting versions = 1.0.0. It is fixed in 1.1.0. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
- Which versions of namada-apps are affected by GHSA-82VG-5V4F-F9WQ? namada-apps (rust) versions = 1.0.0 is affected.
- Is there a fix for GHSA-82VG-5V4F-F9WQ? Yes. GHSA-82VG-5V4F-F9WQ is fixed in 1.1.0. Upgrade to this version or later.
- Is GHSA-82VG-5V4F-F9WQ exploitable, and should I be worried? Whether GHSA-82VG-5V4F-F9WQ 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 GHSA-82VG-5V4F-F9WQ 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 GHSA-82VG-5V4F-F9WQ? Upgrade
namada-appsto 1.1.0 or later.