How severe is GHSA-hrjv-pf36-jpmr?

No CVSS score has been assigned to GHSA-hrjv-pf36-jpmr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hrjv-pf36-jpmr?

GHSA-hrjv-pf36-jpmr affects the following packages: oqs (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-hrjv-pf36-jpmr?

Update oqs to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrjv-pf36-jpmr is resolved across your whole dependency graph.

How do I detect GHSA-hrjv-pf36-jpmr in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oqs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hrjv-pf36-jpmr if there is no patch (or I can't update yet)?

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.

Is GHSA-hrjv-pf36-jpmr actively exploited in the wild?

No public exploit code has been indexed for GHSA-hrjv-pf36-jpmr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hrjv-pf36-jpmr published, and has it been updated?

GHSA-hrjv-pf36-jpmr was published on August 18, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

oqs's Post-Quantum Key Encapsulation Mechanism SIKE…

Real-World Exposure

1 pkg affected

🦀oqs

Real-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

Wouter Castryck and Thomas Decru presented an efficient key recovery attack on the SIDH protocol. As a result, the secret key of SIKEp751 can be recovered in a matter of hours. The SIKE and SIDH schemes will be removed from oqs 0.7.2.

An efficient key recovery attack on SIDH (preliminary version)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`oqs`	all versions	0.7.2`cargo update -p oqs --precise 0.7.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oqs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update oqs to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrjv-pf36-jpmr 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

Wouter Castryck and Thomas Decru presented an efficient key recovery attack on the SIDH protocol. As a result, the secret key of SIKEp751 can be recovered in a matter of hours. The SIKE and SIDH schemes will be removed from oqs 0.7.2. [An efficient key recovery attack on SIDH (preliminary version)](https://eprint.iacr.org/2022/975)

O3 Security · Impact-Aware SCA

Is GHSA-hrjv-pf36-jpmr in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

oqs's Post-Quantum Key Encapsulation Mechanism SIKE brokenGHSA-hrjv-pf36-jpmr