Skip to main content

rust-openssl CVE-2026-42327

| EUVD-2026-30474 HIGH
Improper Input Validation (CWE-20)
2026-05-05 https://github.com/rust-openssl/rust-openssl GHSA-xp3w-r5p5-63rr
8.7
CVSS 4.0
Share

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
X

Lifecycle Timeline

5
Analysis Updated
May 14, 2026 - 21:28 vuln.today
v2 (cvss_changed)
Re-analysis Queued
May 14, 2026 - 21:22 vuln.today
cvss_changed
CVSS changed
May 14, 2026 - 21:22 NVD
8.7 (HIGH)
Source Code Evidence Fetched
May 05, 2026 - 22:30 vuln.today
Analysis Generated
May 05, 2026 - 22:30 vuln.today

DescriptionNVD

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.

AnalysisAI

Undefined behavior in rust-openssl's X509Ref::ocsp_responders allows crafted X.509 certificates with non-UTF-8 OCSP responder URLs to violate Rust's memory safety guarantees. Applications parsing untrusted certificates (TLS handshakes, certificate validation pipelines, PKI tooling) can trigger undefined behavior through safe Rust code when processing malformed AIA extensions. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Identify all internal applications and dependencies using rust-openssl versions prior to 0.10.79 via package manifests and vulnerability scanning tools. Within 7 days: Upgrade rust-openssl to version 0.10.79 or later and rebuild all affected application binaries; coordinate testing in staging environments to confirm TLS functionality post-update. …

Sign in for detailed remediation steps.

Vendor StatusVendor

Share

CVE-2026-42327 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy