safe_pqc_kyber leaks parts of secret keysGHSA-p4v8-jgcv-9g75
Fix: bwesterb/argyle-kyber@b5c6ad1GHSA-p4v8-jgcv-9g75 is a security vulnerability in safe_pqc_kyber. A fix is available for safe_pqc_kyber — see the affected versions and patch details below.
Real-World Exposure
safe_pqc_kyberReal-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
On some platforms, when an attacker can time decapsulation, and in particular when the attacker can forge cipher texts, they can learn (parts of) the secret key.
Does not apply to ephemeral usage, such as when used in the regular way in TLS.
Patches
Patched in 0.6.2.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | safe_pqc_kyber | all versions | 0.6.2cargo update -p safe_pqc_kyber --precise 0.6.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for safe_pqc_kyber, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update safe_pqc_kyber to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p4v8-jgcv-9g75 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.
Frequently Asked Questions
Is GHSA-p4v8-jgcv-9g75 in your dependencies?
Find it across crates.io, including transitive dependencies.