Bug 2559994 - CVE-2026-93601 selenium-manager: rustls-webpki: Name Constraint Bypass in wildcard certificate validation [fedora-all]
Summary: CVE-2026-93601 selenium-manager: rustls-webpki: Name Constraint Bypass in wil...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selenium-manager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: TomasJuhasz
QA Contact:
URL:
Whiteboard: {"flaws": ["94568926-7455-4c8f-8f71-6...
Depends On:
Blocks: CVE-2026-93601
TreeView+ depends on / blocked
 
Reported: 2026-10-23 15:59 UTC by Ronit Dey
Modified: 2026-10-26 19:51 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-26 19:51:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ronit Dey 2026-10-23 15:59:47 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Ben Beasley 2026-10-26 19:51:55 UTC
See https://www.cve.org/CVERecord?id=CVE-2026-93601.

I’ve just rebuilt this package in all branches for https://forge.fedoraproject.org/rust/backlog/issues/43 and https://forge.fedoraproject.org/rust/backlog/issues/46, which guarantees that it was also rebuilt with rustls-webpki 0.103.16; the fix was in 0.103.12.


Note You need to log in before you can comment on or make changes to this bug.