<?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>Tue, 06 Oct 2026 15:47:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-280495</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-280495</link>
      <description>EUVD-2026-280495</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-280495</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34950</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34950</link>
      <description>&lt;p&gt;fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, the publicKeyPemMatcher regex in fast-jwt/src/crypto.js uses a ^ anchor that is defeated by any leading whitespace in the key string, re-enabling the exact same JWT algorithm confusion attack that CVE-2023-48223 patched.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, the publicKeyPemMatcher regex in fast-jwt/src/crypto.js uses a ^ anchor that is defeated by any leading whitespace in the key string, re-enabling the exact same JWT algorithm confusion attack that CVE-2023-48223 patched.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34950</guid>
    </item>
    <item>
      <title>GHSA-mvf2-f6gm-w987 — fast-jwt: Incomplete fix for CVE-2023-48223: JWT Algorithm Confusion via Whitespace-Prefixed RSA Public Key</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mvf2-f6gm-w987</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fast-jwt&lt;/p&gt;
&lt;p&gt;### Summary
 The fix for GHSA-c2ff-88x2-x9pg (CVE-2023-48223) is incomplete. The publicKeyPemMatcher regex in fast-jwt/src/crypto.js uses a ^ anchor that is defeated by any leading whitespace in the key string, re-enabling the exact same JWT algorithm confusion attack that the CVE patched.&lt;/p&gt;
&lt;p&gt;### Details
 The fix for CVE-2023-48223 (https://github.com/nearform/fast-jwt/commit/15a6e92, v3.3.2) changed the public key matcher from a
  plain string used with .includes() to a regex used with .match():&lt;/p&gt;
&lt;p&gt;```
  // Before fix (vulnerable to original CVE)
  const publicKeyPemMatcher = &amp;#39;-----BEGIN PUBLIC KEY-----&amp;#39;
  // .includes() matched anywhere in the string — not vulnerable to whitespace&lt;/p&gt;
&lt;p&gt;// After fix (current code, line 28)
  const publicKeyPemMatcher = /^-----BEGIN(?: (RSA))? PUBLIC KEY-----/
  // ^ anchor requires match at position 0 — defeated by leading whitespace&lt;/p&gt;
&lt;p&gt;In performDetectPublicKeyAlgorithms()
  (https://github.com/nearform/fast-jwt/blob/0ff14a687b9af786bd3ffa870d6febe6e1f13aaa/src/crypto.js#L126-L137):&lt;/p&gt;
&lt;p&gt;function performDetectPublicKeyAlgorithms(key) {
    const publicKeyPemMatch = key.match(publicKeyPemMatcher)  // no .trim()!&lt;/p&gt;
&lt;p&gt;if (key.match(privateKeyPemMatcher)) {
      throw ...
    } else if (publicKeyPemMatch &amp;amp;&amp;amp; publicKeyPemMatch[1] === &amp;#39;RSA&amp;#39;) {
      return rsaAlgorithms      // ← correct path: restricts to RS/PS algorithms
    } else if (!publicKeyPemMatch &amp;amp;&amp;amp; !key.includes(publicKeyX509CertMatcher)) {
      return hsAlgorithms        // ← VULNERABLE: R…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fast-jwt&lt;/p&gt;
&lt;p&gt;### Summary
 The fix for GHSA-c2ff-88x2-x9pg (CVE-2023-48223) is incomplete. The publicKeyPemMatcher regex in fast-jwt/src/crypto.js uses a ^ anchor that is defeated by any leading whitespace in the key string, re-enabling the exact same JWT algorithm confusion attack that the CVE patched.&lt;/p&gt;
&lt;p&gt;### Details
 The fix for CVE-2023-48223 (https://github.com/nearform/fast-jwt/commit/15a6e92, v3.3.2) changed the public key matcher from a
  plain string used with .includes() to a regex used with .match():&lt;/p&gt;
&lt;p&gt;```
  // Before fix (vulnerable to original CVE)
  const publicKeyPemMatcher = &amp;#39;-----BEGIN PUBLIC KEY-----&amp;#39;
  // .includes() matched anywhere in the string — not vulnerable to whitespace&lt;/p&gt;
&lt;p&gt;// After fix (current code, line 28)
  const publicKeyPemMatcher = /^-----BEGIN(?: (RSA))? PUBLIC KEY-----/
  // ^ anchor requires match at position 0 — defeated by leading whitespace&lt;/p&gt;
&lt;p&gt;In performDetectPublicKeyAlgorithms()
  (https://github.com/nearform/fast-jwt/blob/0ff14a687b9af786bd3ffa870d6febe6e1f13aaa/src/crypto.js#L126-L137):&lt;/p&gt;
&lt;p&gt;function performDetectPublicKeyAlgorithms(key) {
    const publicKeyPemMatch = key.match(publicKeyPemMatcher)  // no .trim()!&lt;/p&gt;
&lt;p&gt;if (key.match(privateKeyPemMatcher)) {
      throw ...
    } else if (publicKeyPemMatch &amp;amp;&amp;amp; publicKeyPemMatch[1] === &amp;#39;RSA&amp;#39;) {
      return rsaAlgorithms      // ← correct path: restricts to RS/PS algorithms
    } else if (!publicKeyPemMatch &amp;amp;&amp;amp; !key.includes(publicKeyX509CertMatcher)) {
      return hsAlgorithms        // ← VULNERABLE: R…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mvf2-f6gm-w987</guid>
    </item>
  </channel>
</rss>
