Bug 2559996 - CVE-2026-93601 sandogasa: rustls-webpki: Name Constraint Bypass in wildcard certificate validation [epel-all]
Summary: CVE-2026-93601 sandogasa: rustls-webpki: Name Constraint Bypass in wildcard c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: sandogasa
Version: epel10
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Michel Lind
QA Contact:
URL:
Whiteboard: {"flaws": ["94568926-7455-4c8f-8f71-6...
Depends On:
Blocks: CVE-AlreadyFixed CVE-2026-93601
TreeView+ depends on / blocked
 
Reported: 2026-10-23 16:00 UTC by Ronit Dey
Modified: 2026-11-05 22:12 UTC (History)
2 users (show)

Fixed In Version: sandogasa-0.11.3-1.el10_2 sandogasa-0.16.0-2.el10_3 sandogasa-0.16.0-2.el9
Clone Of:
Environment:
Last Closed: 2026-11-05 22:11:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ronit Dey 2026-10-23 16:00: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 Michel Lind 2026-11-05 22:11:54 UTC
This bug is already fixed in published Bodhi updates, one per release it covers:
  sandogasa-0.11.3-1.el10_2
  sandogasa-0.16.0-2.el10_3
  sandogasa-0.16.0-2.el9

Comment 2 Michel Lind 2026-11-05 22:12:21 UTC
This bug is already fixed in a published Bodhi update.


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