Bug 2548171 - CVE-2026-93600 sandogasa: rustls-webpki: URI Name Constraint Bypass via X.509 Certificate Misissue [epel-all]
Summary: CVE-2026-93600 sandogasa: rustls-webpki: URI Name Constraint Bypass via X.509...
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": ["ab1878dc-6ee9-4241-bf74-8...
Depends On:
Blocks: CVE-AlreadyFixed CVE-2026-93600
TreeView+ depends on / blocked
 
Reported: 2026-10-08 18:50 UTC by Ganesh
Modified: 2026-10-13 16:10 UTC (History)
2 users (show)

Fixed In Version: sandogasa-0.11.3-1.el10_2 sandogasa-0.14.0-1.el10_3 sandogasa-0.14.0-1.el9
Clone Of:
Environment:
Last Closed: 2026-10-13 16:10:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-10-08 18:50:04 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 (rustls/webpki) versions 0.101.0 through 0.103.11 and 0.104.0-alpha releases before 0.104.0-alpha.6 ignore X.509 name constraints that apply to URI names, causing such constraints to be accepted rather than enforced. Because name constraints are restrictions on otherwise properly issued certificates, the flaw is only reachable after successful signature verification and requires a misissued certificate to exploit; the library also provides no API for asserting URI names, and URI name constraints are otherwise unimplemented. Versions 0.103.12 and 0.104.0-alpha.6 reject URI name constraints unconditionally.

Comment 1 Michel Lind 2026-10-13 16:10:44 UTC
This bug is already fixed in published Bodhi updates, one per release it covers:
  sandogasa-0.11.3-1.el10_2
  sandogasa-0.14.0-1.el10_3
  sandogasa-0.14.0-1.el9

Comment 2 Michel Lind 2026-10-13 16:10:48 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.