https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T17:24:38.650519+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2026-93601 CVE-2026-93601 — rustls webpki 0.101.0 before 0.103.12 Name Constraint Bypass 2026-10-02T17:24:38.652206+00:00

Affected: rustls webpki

rustls-webpki (the Rust webpki fork used by rustls) versions >= 0.101.0 and prior to 0.103.12 and 0.104.0-alpha.6 incorrectly accepted permitted-subtree DNS name constraints for certificates asserting a wildcard name. For example, a name constraint of accept.example.com was treated as satisfied by a certificate for *.example.com, which could feasibly assert reject.example.com — a name outside the permitted subtree. Because name constraints are restrictions applied to otherwise properly issued certificates, the issue is only reachable after signature verification succeeds and requires a misissued wildcard certificate to exploit.

 https://cve.radiocsirt.org/vuln/ghsa-xgp8-3hg3-c2mh GHSA-xgp8-3hg3-c2mh — webpki: Name constraints were accepted for certificates asserting a wildcard name 2026-10-02T17:24:38.652266+00:00

Affected: crates.io: rustls-webpki

Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.

This 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. This is very similar to [CVE-2025-61727](https://go.dev/issue/76442).

Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.