<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 07:37:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93599 — rustls-webpki before 0.103.13 Panic via empty BIT STRING</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-93599</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rustls webpki&lt;/p&gt;
&lt;p&gt;rustls-webpki through 0.103.12 (and 0.104.0-alpha releases before 0.104.0-alpha.7) contains a reachable panic in bit_string_flags() in src/der.rs. The input guard fails to reject a named-bit BIT STRING whose content is exactly [0x00] (zero padding bits and no data bytes), so raw_bits.len() - 1 underflows on the empty slice and the subsequent index operation panics (subtract-with-overflow in debug, index-out-of-bounds in release). The condition is reachable through the public API BorrowedCertRevocationList::from_der() when a CRL contains an issuingDistributionPoint extension with such an onlySomeReasons value. Exploitation requires an application that explicitly opts in to CRL revocation checking by passing RevocationOptions to verify_for_usage() and that parses CRL bytes obtained from a source the attacker can influence; the default rustls configuration, which does not use RevocationOptions, is unaffected. A crafted CRL causes a denial of service via the panic. Fixed in 0.103.13 and 0.104.0-alpha.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rustls webpki&lt;/p&gt;
&lt;p&gt;rustls-webpki through 0.103.12 (and 0.104.0-alpha releases before 0.104.0-alpha.7) contains a reachable panic in bit_string_flags() in src/der.rs. The input guard fails to reject a named-bit BIT STRING whose content is exactly [0x00] (zero padding bits and no data bytes), so raw_bits.len() - 1 underflows on the empty slice and the subsequent index operation panics (subtract-with-overflow in debug, index-out-of-bounds in release). The condition is reachable through the public API BorrowedCertRevocationList::from_der() when a CRL contains an issuingDistributionPoint extension with such an onlySomeReasons value. Exploitation requires an application that explicitly opts in to CRL revocation checking by passing RevocationOptions to verify_for_usage() and that parses CRL bytes obtained from a source the attacker can influence; the default rustls configuration, which does not use RevocationOptions, is unaffected. A crafted CRL causes a denial of service via the panic. Fixed in 0.103.13 and 0.104.0-alpha.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-93599</guid>
    </item>
    <item>
      <title>GHSA-82j2-j2ch-gfr8 — rustls-webpki: Denial of service via panic on malformed CRL BIT STRING</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-82j2-j2ch-gfr8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rustls-webpki&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`bit_string_flags()` in `src/der.rs` panics with an index-out-of-bounds when given a BIT STRING whose content is exactly `[0x00]` (one byte: zero padding bits, zero data bytes). This is reachable through the public API `BorrowedCertRevocationList::from_der()` via the `issuingDistributionPoint` CRL extension.&lt;/p&gt;
&lt;p&gt;**Precondition**: CRL checking is opt-in in rustls-webpki. This vulnerability affects only applications that explicitly pass `RevocationOptions` to `verify_for_usage()` and load CRL bytes from a source the attacker can influence. The default rustls configuration (no `RevocationOptions`) is not affected.&lt;/p&gt;
&lt;p&gt;&amp;gt; **AI disclosure**: This report was prepared with AI assistance (Claude). The vulnerability was discovered by differential fuzzing against a formally-verified Rust oracle. All technical claims have been independently verified against the live source code before submission.&lt;/p&gt;
&lt;p&gt;### Details
`bit_string_flags()` in `src/der.rs` reads the content of named-bit BIT
STRINGs (KeyUsage, ReasonFlags, etc.). Its input guard:&lt;/p&gt;
&lt;p&gt;```rust
if padding_bits &amp;gt; 7 || (raw_bits.is_empty() &amp;amp;&amp;amp; padding_bits != 0) {
    return Err(Error::BadDer);
}
let last_byte = raw_bits[raw_bits.len() - 1];  // ← crash
```
misses the case `padding_bits == 0 &amp;amp;&amp;amp; raw_bits.is_empty()`.
When a BIT STRING has content `[0x00]`  (one padding-bits byte set to zero, no data bytes):
- padding_bits = 0x00 — passes the &amp;gt; 7 check ✓
- raw_bits = [] — passes is_empty() &amp;amp;&amp;amp; != 0 check ✓ (because 0 != 0 is false)
- ra…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rustls-webpki&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`bit_string_flags()` in `src/der.rs` panics with an index-out-of-bounds when given a BIT STRING whose content is exactly `[0x00]` (one byte: zero padding bits, zero data bytes). This is reachable through the public API `BorrowedCertRevocationList::from_der()` via the `issuingDistributionPoint` CRL extension.&lt;/p&gt;
&lt;p&gt;**Precondition**: CRL checking is opt-in in rustls-webpki. This vulnerability affects only applications that explicitly pass `RevocationOptions` to `verify_for_usage()` and load CRL bytes from a source the attacker can influence. The default rustls configuration (no `RevocationOptions`) is not affected.&lt;/p&gt;
&lt;p&gt;&amp;gt; **AI disclosure**: This report was prepared with AI assistance (Claude). The vulnerability was discovered by differential fuzzing against a formally-verified Rust oracle. All technical claims have been independently verified against the live source code before submission.&lt;/p&gt;
&lt;p&gt;### Details
`bit_string_flags()` in `src/der.rs` reads the content of named-bit BIT
STRINGs (KeyUsage, ReasonFlags, etc.). Its input guard:&lt;/p&gt;
&lt;p&gt;```rust
if padding_bits &amp;gt; 7 || (raw_bits.is_empty() &amp;amp;&amp;amp; padding_bits != 0) {
    return Err(Error::BadDer);
}
let last_byte = raw_bits[raw_bits.len() - 1];  // ← crash
```
misses the case `padding_bits == 0 &amp;amp;&amp;amp; raw_bits.is_empty()`.
When a BIT STRING has content `[0x00]`  (one padding-bits byte set to zero, no data bytes):
- padding_bits = 0x00 — passes the &amp;gt; 7 check ✓
- raw_bits = [] — passes is_empty() &amp;amp;&amp;amp; != 0 check ✓ (because 0 != 0 is false)
- ra…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-82j2-j2ch-gfr8</guid>
    </item>
  </channel>
</rss>
