CVE-2026-93601

rustls webpki 0.101.0 before 0.103.12 Name Constraint Bypass

Published Sep 18, 2026 CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability is caused by rustls/webpki misinterpreting name‑constraint rules when validating certificates that contain a wildcard subject. A permitted‑subtree constraint such as accept.example.com is evaluated as satisfied by a certificate for *.example.com, even though a certificate for reject.example.com, which is outside the intended subtree, can also be represented by the same wildcard. This flaw is only reachable after the certificate’s signature has been verified, and thus requires a misissued wildcard certificate that matches the domain. The flaw aligns with CWE-1289 and CWE-295.

Affected Systems

The affected component is the rustls/webpki library used by the Rust ecosystem for TLS certificate validation. Versions 0.101.0 through 0.103.11 inclusive, as well as 0.104.0‑alpha.6, are vulnerable. Any Rust application that links to one of these library versions, including servers and clients that rely on rustls for secure connections, is impacted until the library is upgraded to 0.103.12 or later.

Risk and Exploitability

The CVSS score of 2.1 indicates low severity, and the EPSS score of < 1% indicates a very low probability of exploitation. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires a misissued wildcard certificate that passes initial signature checks and a system that enforces name‑constraint validation. Because the flaw only becomes active after the certificate passes normal integrity checks, the attack surface is limited to scenarios where strict name‑constraint enforcement is used; nevertheless, a successful bypass could allow an attacker to impersonate a domain trusted by the application. The weakness is formally identified as CWE-1289 and CWE-295.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade rustls/webpki to 0.103.12 or a later compatible release that implements correct name‑constraint validation.
  • Rebuild and redeploy all Rust applications that depend on rustls, ensuring that Cargo.lock and any dependency resolution points to the patched version.
  • If an immediate upgrade cannot be performed, modify the application’s TLS configuration or certificate handling logic to reject wildcard certificates when name‑constraints are present, or disable name‑constraint processing for those certificates.
  • Run a comprehensive dependency audit to confirm that no module or indirect dependency still pulls in the vulnerable library version and verify that the updated code is deployed across all affected environments.

Generated by OpenCVE AI on September 23, 2026 at 01:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Rustls
Rustls webpki
Vendors & Products Rustls
Rustls webpki
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title rustls webpki 0.101.0 before 0.103.12 Name Constraint Bypass
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 2.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-1289

    Improper Validation of Unsafe Equivalence in Input

  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 18, 2026, 5:49 PM
Reserved
Sep 18, 2026, 11:00 AM
Status
Awaiting Analysis
Published
Sep 18, 2026, 2:19 PM
Modified
Sep 22, 2026, 8:25 PM
Severity
Low
Public date
Sep 18, 2026, 1:20 PM