How severe is GHSA-xp3w-r5p5-63rr?

No CVSS score has been assigned to GHSA-xp3w-r5p5-63rr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xp3w-r5p5-63rr?

GHSA-xp3w-r5p5-63rr affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-xp3w-r5p5-63rr?

Update openssl to 0.10.79 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xp3w-r5p5-63rr is resolved across your whole dependency graph.

How do I detect GHSA-xp3w-r5p5-63rr in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xp3w-r5p5-63rr 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-xp3w-r5p5-63rr?

O3 pinpoints whether GHSA-xp3w-r5p5-63rr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xp3w-r5p5-63rr actively exploited in the wild?

No public exploit code has been indexed for GHSA-xp3w-r5p5-63rr 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-xp3w-r5p5-63rr published, and has it been updated?

GHSA-xp3w-r5p5-63rr was published on May 5, 2026 and was last updated on May 16, 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-xp3w-r5p5-63rr

GHSA-xp3w-r5p5-63rr is a security vulnerability in openssl. O3 Security confirms whether GHSA-xp3w-r5p5-63rr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

rust-openssl has undefined behavior in X509Ref::ocsp_responders for certificates with non-UTF-8 OCSP URLs

Also known asCVE-2026-42327

Published

May 5, 2026

Updated

May 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

X509Ref::ocsp_responders returns OCSP responder URLs from a certificate's AIA extension as OpensslString, whose Deref<Target = str> wraps the raw bytes with str::from_utf8_unchecked. OpenSSL does not enforce that the underlying IA5String is ASCII, so a certificate with non-UTF-8 bytes in its OCSP accessLocation causes safe Rust code to construct a &str that violates the UTF-8 invariant — resulting in undefined behavior.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	≥ 0.9.7&&< 0.10.79	0.10.79

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openssl to 0.10.79 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xp3w-r5p5-63rr 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 pinpoints whether GHSA-xp3w-r5p5-63rr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xp3w-r5p5-63rr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`X509Ref::ocsp_responders` returns OCSP responder URLs from a certificate's AIA extension as `OpensslString`, whose `Deref<Target = str>` wraps the raw bytes with `str::from_utf8_unchecked`. OpenSSL does not enforce that the underlying IA5String is ASCII, so a certificate with non-UTF-8 bytes in its OCSP accessLocation causes safe Rust code to construct a `&str` that violates the UTF-8 invariant — resulting in undefined behavior.

O3 Security · Impact-Aware SCA

Is GHSA-xp3w-r5p5-63rr in your dependencies?

O3 detects GHSA-xp3w-r5p5-63rr 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 dependencies How O3 SCA works