GHSA-2gw2-qgjg-xh6p — namada-apps
GHSA-2gw2-qgjg-xh6p 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 Post-Genesis Validator Bypass
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
Ledger crash. A user is able to initialize a post-genesis validator with a negative commission rate using the --force flag. If this validator gets into the consensus set, then when computing PoS inflation inside fn update_rewards_products_and_mint_inflation, an instance of mul_floor will cause the return of an Err, which causes finalize_block to error.
Patches
This issue has been patched in apps version 1.1.0. The PoS validity predicate now enforces that the commission rate is not negative and any transaction that fails the check will be rejected, both for newly initialized validators and for commission rate change of an existing validator.
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-2gw2-qgjg-xh6p 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-2gw2-qgjg-xh6p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2gw2-qgjg-xh6p. 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-2gw2-qgjg-xh6p in your dependencies?
O3 Security finds GHSA-2gw2-qgjg-xh6p across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.