How severe is GHSA-h4gh-qq45-vh27?

No CVSS score has been assigned to GHSA-h4gh-qq45-vh27 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h4gh-qq45-vh27?

GHSA-h4gh-qq45-vh27 affects the following packages: cryptography (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-h4gh-qq45-vh27?

Update cryptography to 43.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4gh-qq45-vh27 is resolved across your whole dependency graph.

How do I detect GHSA-h4gh-qq45-vh27 in my PyPI dependencies?

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

How do I mitigate GHSA-h4gh-qq45-vh27 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-h4gh-qq45-vh27?

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

Is GHSA-h4gh-qq45-vh27 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h4gh-qq45-vh27 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-h4gh-qq45-vh27 published, and has it been updated?

GHSA-h4gh-qq45-vh27 was published on September 3, 2024 and was last updated on September 10, 2026. 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

GHSA-h4gh-qq45-vh27 — cryptography

GHSA-h4gh-qq45-vh27 is a security vulnerability in cryptography. A fix is available for cryptography — see the affected versions and patch details below.

pyca/cryptography has a vulnerable OpenSSL included in cryptography wheels

Published

Sep 3, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍cryptography

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

If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cryptography`	≥ 37.0.0&&< 43.0.1	43.0.1`pip install --upgrade 'cryptography==43.0.1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cryptography, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cryptography to 43.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4gh-qq45-vh27 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-h4gh-qq45-vh27 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h4gh-qq45-vh27. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 37.0.0-43.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20240903.txt. If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.

O3 Security · Impact-Aware SCA

Is GHSA-h4gh-qq45-vh27 in your dependencies?

O3 Security finds GHSA-h4gh-qq45-vh27 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