{"id":"RUSTSEC-2026-0474","revision":"0ec724486d28487d90b127443c6df42a","records":[{"revision":"0ec724486d28487d90b127443c6df42a","observedAt":"2026-11-10T14:21:29.97+00:00","statement":{"source":"osv","id":"RUSTSEC-2026-0474","aliases":["CVE-2026-42327","GHSA-xp3w-r5p5-63rr"],"title":"`X509Ref::ocsp_responders` can produce a `&str` that is not valid UTF-8","description":"`X509Ref::ocsp_responders` returns the OCSP responder URLs from a certificate's Authority Information Access extension as `OpensslString` values, which dereference to `str` without validating the bytes. OpenSSL does not require these IA5String values to be ASCII, so for a certificate with non-UTF-8 bytes in an OCSP access location, safe code ends up holding a `&str` that is not valid UTF-8, which is undefined behavior. Certificates often come from untrusted peers.\n\n`ocsp_responders` was added in 0.9.7. 0.10.79 checks each URL and returns an error if it is not valid UTF-8.","state":0,"publishedAt":"2026-05-04T12:00:00+00:00","modifiedAt":"2026-11-10T14:00:02.466676+00:00","affected":[{"ecosystem":"crates.io","name":"openssl","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.9.7"},{"kind":"fixed","version":"0.10.79"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://crates.io/crates/openssl","https://rustsec.org/advisories/RUSTSEC-2026-0474.html","https://github.com/rust-openssl/rust-openssl/pull/2631"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2026-0474","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2026-0474","identifiers":["RUSTSEC-2026-0474","CVE-2026-42327","GHSA-xp3w-r5p5-63rr"]},"retained":false,"historicalAffected":[]}],"coverage":[]}