<?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 11:36:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276752</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276752</link>
      <description>EUVD-2026-276752</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276752</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33129</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33129</link>
      <description>&lt;p&gt;H3 is a minimal H(TTP) framework. Versions 2.0.1-beta.0 through 2.0.0-rc.8 contain a Timing Side-Channel vulnerability in the requireBasicAuth function due to the use of unsafe string comparison (!==). This allows an attacker to deduce the valid password character-by-character by measuring the server&amp;#39;s response time, effectively bypassing password complexity protections. This issue is fixed in version 2.0.1-rc.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;H3 is a minimal H(TTP) framework. Versions 2.0.1-beta.0 through 2.0.0-rc.8 contain a Timing Side-Channel vulnerability in the requireBasicAuth function due to the use of unsafe string comparison (!==). This allows an attacker to deduce the valid password character-by-character by measuring the server&amp;#39;s response time, effectively bypassing password complexity protections. This issue is fixed in version 2.0.1-rc.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33129</guid>
    </item>
    <item>
      <title>GHSA-26f5-8h2x-34xh — h3 has an observable timing discrepancy in basic auth utils</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-26f5-8h2x-34xh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: h3&lt;/p&gt;
&lt;p&gt;### Summary
A Timing Side-Channel vulnerability exists in the `requireBasicAuth` function due to the use of unsafe string comparison (`!==`). This allows an attacker to deduce the valid password character-by-character by measuring the server&amp;#39;s response time, effectively bypassing password complexity protections.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is located in the `requireBasicAuth` function. The code performs a standard string comparison between the user-provided password and the expected password:&lt;/p&gt;
&lt;p&gt;~~~typescript
if (opts.password &amp;amp;&amp;amp; password !== opts.password) {
  throw autheFailed(event, opts?.realm);
}
~~~&lt;/p&gt;
&lt;p&gt;In V8 (and most runtime environments), the `!==` operator is optimized to &amp;#34;fail fast.&amp;#34; It stops execution and returns `false` as soon as it encounters the first mismatched byte.
* If the first character is wrong, it returns immediately.
* If the first character is correct but the second is wrong, it takes slightly longer.&lt;/p&gt;
&lt;p&gt;By statistically analyzing these minute timing differences over many requests, an attacker can determine the correct password one character at a time.&lt;/p&gt;
&lt;p&gt;### PoC
This vulnerability is exploitable in real-world scenarios without direct access to the server machine.&lt;/p&gt;
&lt;p&gt;To reproduce this, an attacker can send two packets (or bursts of packets) at the exact same time:
1.  **Packet A:** Contains a password that is known to be incorrect starting at the first character (e.g., `AAAA...`).
2.  **Packet B:** Contains a password where the first character is a guess (e…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: h3&lt;/p&gt;
&lt;p&gt;### Summary
A Timing Side-Channel vulnerability exists in the `requireBasicAuth` function due to the use of unsafe string comparison (`!==`). This allows an attacker to deduce the valid password character-by-character by measuring the server&amp;#39;s response time, effectively bypassing password complexity protections.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is located in the `requireBasicAuth` function. The code performs a standard string comparison between the user-provided password and the expected password:&lt;/p&gt;
&lt;p&gt;~~~typescript
if (opts.password &amp;amp;&amp;amp; password !== opts.password) {
  throw autheFailed(event, opts?.realm);
}
~~~&lt;/p&gt;
&lt;p&gt;In V8 (and most runtime environments), the `!==` operator is optimized to &amp;#34;fail fast.&amp;#34; It stops execution and returns `false` as soon as it encounters the first mismatched byte.
* If the first character is wrong, it returns immediately.
* If the first character is correct but the second is wrong, it takes slightly longer.&lt;/p&gt;
&lt;p&gt;By statistically analyzing these minute timing differences over many requests, an attacker can determine the correct password one character at a time.&lt;/p&gt;
&lt;p&gt;### PoC
This vulnerability is exploitable in real-world scenarios without direct access to the server machine.&lt;/p&gt;
&lt;p&gt;To reproduce this, an attacker can send two packets (or bursts of packets) at the exact same time:
1.  **Packet A:** Contains a password that is known to be incorrect starting at the first character (e.g., `AAAA...`).
2.  **Packet B:** Contains a password where the first character is a guess (e…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-26f5-8h2x-34xh</guid>
    </item>
  </channel>
</rss>
