How severe is GHSA-hvh4-5qr6-3v7r?

GHSA-hvh4-5qr6-3v7r has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hvh4-5qr6-3v7r?

GHSA-hvh4-5qr6-3v7r affects the following packages: pypqc (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-hvh4-5qr6-3v7r?

No patched version of pypqc has shipped for GHSA-hvh4-5qr6-3v7r yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-hvh4-5qr6-3v7r in my PyPI dependencies?

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

How do I mitigate GHSA-hvh4-5qr6-3v7r 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.

How does O3 Security protect against GHSA-hvh4-5qr6-3v7r?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hvh4-5qr6-3v7r can be triaged on real exposure rather than presence alone.

Is GHSA-hvh4-5qr6-3v7r actively exploited in the wild?

No public exploit code has been indexed for GHSA-hvh4-5qr6-3v7r 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-hvh4-5qr6-3v7r published, and has it been updated?

GHSA-hvh4-5qr6-3v7r was published on June 5, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

GHSA-hvh4-5qr6-3v7r — pypqc

HIGH

GHSA-hvh4-5qr6-3v7r is a high-severity (CVSS 8.2) vulnerability in pypqc. No vendor fix is recorded yet; mitigation options are listed below.

Observable Timing Discrepancy in pypqc

Published

Jun 5, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍pypqc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

kyber512, kyber768, and kyber1024 on Mac OS (or when compiled with clang) only: An attacker able to submit many decapsulation requests against a single private key, and to gain timing information about the decapsulation, could recover the private key. Proof-of-concept exploit exists for a local attacker.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P/RL:U/RC:C

Patches

No patch is currently available / pending upstream PQClean#556.

Workarounds

No workarounds have been reported. The 0.0.7 -> 0.0.7.1 upgrade, when available, should be a drop-in replacement.

References

https://pqshield.com/pqshield-plugs-timing-leaks-in-kyber-ml-kem-to-improve-pqc-implementation-maturity/

https://github.com/antoonpurnal/clangover

https://www.github.com/PQClean/PQClean/issues/556

https://www.github.com/pq-crystals/kyber/commit/9b8d30698a3e7449aeb34e62339d4176f11e3c6c

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pypqc`	≥ 0.0.4	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypqc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of pypqc has shipped for GHSA-hvh4-5qr6-3v7r yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-hvh4-5qr6-3v7r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hvh4-5qr6-3v7r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact `kyber512`, `kyber768`, and `kyber1024` on Mac OS \(or when compiled with clang\) only: An attacker able to submit many decapsulation requests against a single private key, and to gain timing information about the decapsulation, could recover the private key. Proof-of-concept exploit exists for a local attacker. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P/RL:U/RC:C ### Patches No patch is currently available / pending upstream [PQClean#556](https://github.com/PQClean/PQClean/issues/556). ### Workarounds No workarounds have been reported. The 0.0.7 -> 0.0.7.1 upgrade, when

O3 Security · Impact-Aware SCA

Is GHSA-hvh4-5qr6-3v7r in your dependencies?

O3 Security finds GHSA-hvh4-5qr6-3v7r across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works