GHSA-9qmm-4mfr-r3wj
CRITICALGHSA-9qmm-4mfr-r3wj is a critical-severity (CVSS 9.1) CWE-682 vulnerability in solana_rbpf. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-9qmm-4mfr-r3wj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Incorrect Calculation in solana_rbpf
Blast Radius
solana_rbpfReal-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
In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to transfer tokens or not. The vulnerability affects both integrity and may cause serious availability problems.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | solana_rbpf | ≥ 0.2.26&&< 0.2.28 | 0.2.28 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solana_rbpf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update solana_rbpf to 0.2.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qmm-4mfr-r3wj 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 pinpoints whether GHSA-9qmm-4mfr-r3wj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-9qmm-4mfr-r3wj. 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-9qmm-4mfr-r3wj in your dependencies?
O3 detects GHSA-9qmm-4mfr-r3wj across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.