{"affected":[{"database_specific":{"categories":[],"cvss":null,"informational":null,"source":"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0099.json"},"ecosystem_specific":{"affected_functions":null,"affects":{"arch":[],"functions":[],"os":[]}},"package":{"ecosystem":"crates.io","name":"rustls-webpki","purl":"pkg:cargo/rustls-webpki"},"ranges":[{"events":[{"introduced":"0.0.0-0"},{"fixed":"0.103.12"},{"introduced":"0.104.0-alpha.1"},{"fixed":"0.104.0-alpha.6"}],"type":"SEMVER"}]}],"aliases":["CVE-2026-93601","GHSA-xgp8-3hg3-c2mh"],"database_specific":{"license":"CC0-1.0"},"details":"Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.\n\nThis was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint.\nThis is very similar to [CVE-2025-61727](https://go.dev/issue/76442).\n\nSince name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.\n\nThis vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to [@1seal](https://github.com/1seal) for the report.","id":"RUSTSEC-2026-0099","modified":"2026-09-19T08:42:27Z","published":"2026-04-14T12:00:00Z","references":[{"type":"PACKAGE","url":"https://crates.io/crates/rustls-webpki"},{"type":"ADVISORY","url":"https://rustsec.org/advisories/RUSTSEC-2026-0099.html"}],"schema_version":"1.9.0","summary":"Name constraints were accepted for certificates asserting a wildcard name"}