GHSA-f8qm-hmm3-fv7f — namada-apps
GHSA-f8qm-hmm3-fv7f is a security vulnerability in namada-apps. A fix is available for namada-apps — see the affected versions and patch details below.
Namada-apps allows Excessive Computation in Mempool Validation
Real-World Exposure
namada-appsReal-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
Impact
A malicious transaction may cause an expensive computation in mempool validation.
A transaction with multiple repeated sections causes the section hash calculation used for signature validation to grow exponentially (and potentially even cubic) in proportion to number of sections. This may be used to significantly slow down operation of nodes.
Patches
This issue has been patched in apps version 1.1.0. The transaction sections are now being checked for uniqueness and the number of permitted sections contained in a single transaction has been limited to 10,000.
Workarounds
There are no workarounds and users are advised to upgrade.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | namada-apps | ≥ 1.0.0&&< 1.1.0 | 1.1.0cargo update -p namada-apps --precise 1.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for namada-apps, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update namada-apps to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f8qm-hmm3-fv7f 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 GHSA-f8qm-hmm3-fv7f can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f8qm-hmm3-fv7f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f8qm-hmm3-fv7f in your dependencies?
O3 Security finds GHSA-f8qm-hmm3-fv7f across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.