<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T16:49:42.584177+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93601</id>
    <title>fkie_cve-2026-93601</title>
    <updated>2026-10-01T16:49:42.664492+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>rustls-webpki (the Rust webpki fork used by rustls) versions &gt;= 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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-93601"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-27hx-xqx9-p6hq</id>
    <title>GHSA-27hx-xqx9-p6hq</title>
    <updated>2026-10-01T16:49:42.664634+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>rustls-webpki (the Rust webpki fork used by rustls) versions &gt;= 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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-27hx-xqx9-p6hq"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/msrc_cve-2026-93601</id>
    <title>msrc_CVE-2026-93601 — rustls webpki 0.101.0 before 0.103.12 Name Constraint Bypass</title>
    <updated>2026-10-01T16:49:42.664665+00:00</updated>
    <content>msrc_CVE-2026-93601</content>
    <link href="https://vulnerability.circl.lu/vuln/msrc_cve-2026-93601"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11936-1</id>
    <title>openSUSE-SU-2026:11936-1 — python313-tokenizers-0.23.2-1.1 on GA media</title>
    <updated>2026-10-01T16:49:42.664693+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>python313-tokenizers-0.23.2-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/opensuse-su-2026:11936-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rustsec-2026-0099</id>
    <title>RUSTSEC-2026-0099 — Name constraints were accepted for certificates asserting a wildcard name</title>
    <updated>2026-10-01T16:49:42.664719+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: rustls-webpki</p>
<p>Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name.</p>
<p>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).</p>
<p>Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.</p>
<p>This vulnerability is identified as [GHSA-xgp8-3hg3-c2mh](https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh). Thank you to [@1seal](https://github.com/1seal) for the report.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rustsec-2026-0099"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93601</id>
    <title>UBUNTU-CVE-2026-93601</title>
    <updated>2026-10-01T16:49:42.664761+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: rust-rustls-webpki, Ubuntu:26.04:LTS: rust-rustls-webpki</p>
<p>rustls-webpki (the Rust webpki fork used by rustls) versions &gt;= 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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93601"/>
  </entry>
</feed>
