How severe is GHSA-h8jm-2x53-xhp5?

GHSA-h8jm-2x53-xhp5 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h8jm-2x53-xhp5?

GHSA-h8jm-2x53-xhp5 affects the following packages: openssl-src (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-h8jm-2x53-xhp5?

Update openssl-src to version 300.0.11 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-h8jm-2x53-xhp5 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-h8jm-2x53-xhp5, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-h8jm-2x53-xhp5?

GHSA-h8jm-2x53-xhp5 has an EPSS (Exploit Prediction Scoring System) score of 91.2%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-h8jm-2x53-xhp5?

GHSA-h8jm-2x53-xhp5 is classified as CWE-120 (CWE-120). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h8jm-2x53-xhp5 published, and has it been updated?

GHSA-h8jm-2x53-xhp5 was published on November 1, 2022 and was last updated on February 4, 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

GHSA-h8jm-2x53-xhp5

HIGH

X.509 Email Address Variable Length Buffer Overflow

Also known asBIT-node-2022-3786BIT-node-min-2022-3786CVE-2022-3786RUSTSEC-2022-0065

Published

Nov 1, 2022

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

91.2%probability of exploitation in next 30 days

Very High Risk100th percentile+63.85%

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.

Blast Radius

1 pkg affected

🦀openssl-src

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

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the . character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service).

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl-src`	≥ 300.0.0&&< 300.0.11	300.0.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A buffer overrun can be triggered in X.509 certificate verification, spe…

github.comGithubJan 2023

Frequently Asked Questions

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.` character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). I

O3 Security · Impact-Aware SCA

Is GHSA-h8jm-2x53-xhp5 in your stack?

O3 detects GHSA-h8jm-2x53-xhp5 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works