How severe is GHSA-xmgf-hq76-4vx2?

No CVSS score has been assigned to GHSA-xmgf-hq76-4vx2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xmgf-hq76-4vx2?

GHSA-xmgf-hq76-4vx2 affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-xmgf-hq76-4vx2?

Update openssl to 0.10.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xmgf-hq76-4vx2 is resolved across your whole dependency graph.

How do I detect GHSA-xmgf-hq76-4vx2 in my crates.io dependencies?

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

How do I mitigate GHSA-xmgf-hq76-4vx2 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-xmgf-hq76-4vx2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xmgf-hq76-4vx2 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-xmgf-hq76-4vx2?

GHSA-xmgf-hq76-4vx2 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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.

What type of vulnerability is GHSA-xmgf-hq76-4vx2?

GHSA-xmgf-hq76-4vx2 is classified as Out-of-bounds Read (CWE-125), CWE-1284 (CWE-1284). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xmgf-hq76-4vx2 published, and has it been updated?

GHSA-xmgf-hq76-4vx2 was published on April 22, 2026 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.

🦀 crates.io

Not in CISA KEV

rust-opennssl has an Out-of-bounds read in PEM password callback when returning an oversized lengthGHSA-xmgf-hq76-4vx2

Fix: rust-openssl/rust-openssl#2605

GHSA-xmgf-hq76-4vx2 is a Out-of-bounds Read vulnerability in openssl. A fix is available for openssl — see the affected versions and patch details below.

Also known asCVE-2026-41677

Published

Apr 22, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, 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-xmgf-hq76-4vx2.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀openssl

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

rust-openssl provides OpenSSL bindings for the Rust programming language. From 0.9.0 to before 0.10.78, the *_from_pem_callback APIs did not validate the length returned by the user's callback. A password callback that returns a value larger than the buffer it was given can cause some versions of OpenSSL to over-read this buffer. OpenSSL 3.x is not affected by this. This vulnerability is fixed in 0.10.78.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	≥ 0.9.0&&< 0.10.78	0.10.78`cargo update -p openssl --precise 0.10.78`

Affected Products

1 product · 1 configurations

Application

rust-opensslrust-openssl_project

≥ 0.9.0 && < 0.10.78

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl to 0.10.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xmgf-hq76-4vx2 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

The `*_from_pem_callback` APIs did not validate the length returned by the user's callback. A password callback that returns a value larger than the buffer it was given can cause some versions of OpenSSL to over-read this buffer. OpenSSL 3.x is not affected by this.

O3 Security · Impact-Aware SCA

Is GHSA-xmgf-hq76-4vx2 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works