How severe is GHSA-79v4-65xg-pq4g?

No CVSS score has been assigned to GHSA-79v4-65xg-pq4g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-79v4-65xg-pq4g?

GHSA-79v4-65xg-pq4g affects the following packages: cryptography (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-79v4-65xg-pq4g?

Update cryptography to 44.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-79v4-65xg-pq4g is resolved across your whole dependency graph.

How do I detect GHSA-79v4-65xg-pq4g 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-79v4-65xg-pq4g 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-79v4-65xg-pq4g?

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

Is GHSA-79v4-65xg-pq4g actively exploited in the wild?

No public exploit code has been indexed for GHSA-79v4-65xg-pq4g 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.

What is the EPSS score for GHSA-79v4-65xg-pq4g?

GHSA-79v4-65xg-pq4g has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-79v4-65xg-pq4g published, and has it been updated?

GHSA-79v4-65xg-pq4g was published on February 11, 2025 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-79v4-65xg-pq4g — cryptography

Fix: openssl/openssl@738d4f9

GHSA-79v4-65xg-pq4g is a security vulnerability in cryptography. A fix is available for cryptography — see the affected versions and patch details below.

Vulnerable OpenSSL included in cryptography wheels

Also known asCVE-2024-12797PYSEC-2026-1284

Published

Feb 11, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-79v4-65xg-pq4g.

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

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`	≥ 42.0.0&&< 44.0.1	44.0.1`pip install --upgrade 'cryptography==44.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 44.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-79v4-65xg-pq4g 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-79v4-65xg-pq4g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-79v4-65xg-pq4g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2, which was first shipped in RHEL 9.5. Earlier releases of OpenSSL provided in RHEL prior to 9.5 are not affected. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly…

Product	Fixed in	Advisory
Discovery 1 for RHEL 9	`discovery/discovery-server-rhel9:1.12.1-2`	RHSA-2025:1487
Red Hat Enterprise Linux 10	`openssl-1:3.2.2-16.el10`	RHBA-2025:6314
Red Hat Enterprise Linux 9	`openssl-1:3.2.2-6.el9_5.1`	RHSA-2025:1330
RHOL-5.9-RHEL-9	`openshift-logging/cluster-logging-operator-bundle:v5.9.12-13`	RHSA-2025:1985
Service Interconnect 1.4 for RHEL 9	`service-interconnect/skupper-config-sync-rhel9:1.4.8-1`	RHSA-2025:9895
Service Interconnect 1 for RHEL 9	`service-interconnect/skupper-config-sync-rhel9:1.5.5-5`	RHSA-2025:1925
Service Interconnect 1 for RHEL 9	`service-interconnect/skupper-config-sync-rhel9:1.8.5-1`	RHSA-2025:4005
Builds for Red Hat OpenShift 1.3.2	`openshift-builds/openshift-builds-git-cloner-rhel9:1.3.1-1741784043`	RHSA-2025:2754

UbuntuMEDIUM

USN-7264-1Ubuntu

Frequently Asked Questions

pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.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-79v4-65xg-pq4g in your dependencies?

O3 Security finds GHSA-79v4-65xg-pq4g 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