GHSA-9c48-w39g-hm26 — rsa
Fix: RustCrypto/RSA@2926c91GHSA-9c48-w39g-hm26 is a CWE-703 vulnerability in rsa. A fix is available for rsa — see the affected versions and patch details below.
rsa crate has potential panic on a prime being equal to 1
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9c48-w39g-hm26.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
rsaReal-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
When creating a RSA private key from its components, the construction panics, instead of returning an error, when one of the primes is 1.
Discovered by Christian Reitter from Radically Open Security during a security review for Proton AG.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | rsa | all versions | 0.9.10cargo update -p rsa --precise 0.9.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rsa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rsa to 0.9.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9c48-w39g-hm26 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-9c48-w39g-hm26 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9c48-w39g-hm26. 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-9c48-w39g-hm26 in your dependencies?
O3 Security finds GHSA-9c48-w39g-hm26 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.