<?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 12:43:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291012</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291012</link>
      <description>EUVD-2026-291012</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291012</guid>
    </item>
    <item>
      <title>fkie_cve-2026-35040</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35040</link>
      <description>&lt;p&gt;fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.1, using certain modifiers on RegExp objects in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options in verify functions can cause certain unintended behaviours. This is because some modifiers are stateful and will cause failures in every second verification attempt regardless of the validity of the token provided. Such modifiers are /g (global matching) and /y (sticky matching). This does NOT allow invalid tokens to be accepted, only for valid tokens to be improperly rejected in some configurations. Instead it causes 50% of valid authentication requests to fail in an alternating pattern. This vulnerability is fixed in 6.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.1, using certain modifiers on RegExp objects in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options in verify functions can cause certain unintended behaviours. This is because some modifiers are stateful and will cause failures in every second verification attempt regardless of the validity of the token provided. Such modifiers are /g (global matching) and /y (sticky matching). This does NOT allow invalid tokens to be accepted, only for valid tokens to be improperly rejected in some configurations. Instead it causes 50% of valid authentication requests to fail in an alternating pattern. This vulnerability is fixed in 6.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-35040</guid>
    </item>
    <item>
      <title>GHSA-3j8v-cgw4-2g6q — fast-jwt: Stateful RegExp (/g or /y) causes non-deterministic allowed-claim validation (logical DoS)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3j8v-cgw4-2g6q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fast-jwt&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Using certain modifiers on RegExp objects in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options in verify functions can cause certain unintended behaviours. This is because some modifiers are stateful and will cause failures in every second verification attempt regardless of the validity of the token provided.&lt;/p&gt;
&lt;p&gt;Such modifiers are:
- /g : Global matching
- /y : Sticky matching&lt;/p&gt;
&lt;p&gt;This does NOT allow invalid tokens to be accepted, only for valid tokens to be improperly rejected in some configurations. Instead it causes **50% of valid authentication requests to fail** in an alternating pattern, leading to:
  - Intermittent user authentication failures
  - Potential retry storms in applications
  - Operational monitoring alerts&lt;/p&gt;
&lt;p&gt;## Affected Configurations&lt;/p&gt;
&lt;p&gt;### This vulnerability ONLY affects applications that:&lt;/p&gt;
&lt;p&gt;- Use RegExp objects (not strings) in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options
- Use stateful RegExp modifiers such a /g or /y&lt;/p&gt;
&lt;p&gt;Example: allowedAud: /abc/g ← IMPACTED
Example: allowedAud: &amp;#34;/abc/&amp;#34; ← SAFE&lt;/p&gt;
&lt;p&gt;### Not Affected&lt;/p&gt;
&lt;p&gt;- Applications using string patterns for audience validation (most common)
- Applications using RegExp patterns without stateful modifiers&lt;/p&gt;
&lt;p&gt;### Assessment Guide
To determine if you&amp;#39;re affected:&lt;/p&gt;
&lt;p&gt;Check if  allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options use RegExp objects (/pattern/ or new RegExp())
If yes, review the pattern for stateful modifiers like /g, /y
If…&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;## Impact&lt;/p&gt;
&lt;p&gt;Using certain modifiers on RegExp objects in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options in verify functions can cause certain unintended behaviours. This is because some modifiers are stateful and will cause failures in every second verification attempt regardless of the validity of the token provided.&lt;/p&gt;
&lt;p&gt;Such modifiers are:
- /g : Global matching
- /y : Sticky matching&lt;/p&gt;
&lt;p&gt;This does NOT allow invalid tokens to be accepted, only for valid tokens to be improperly rejected in some configurations. Instead it causes **50% of valid authentication requests to fail** in an alternating pattern, leading to:
  - Intermittent user authentication failures
  - Potential retry storms in applications
  - Operational monitoring alerts&lt;/p&gt;
&lt;p&gt;## Affected Configurations&lt;/p&gt;
&lt;p&gt;### This vulnerability ONLY affects applications that:&lt;/p&gt;
&lt;p&gt;- Use RegExp objects (not strings) in the allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options
- Use stateful RegExp modifiers such a /g or /y&lt;/p&gt;
&lt;p&gt;Example: allowedAud: /abc/g ← IMPACTED
Example: allowedAud: &amp;#34;/abc/&amp;#34; ← SAFE&lt;/p&gt;
&lt;p&gt;### Not Affected&lt;/p&gt;
&lt;p&gt;- Applications using string patterns for audience validation (most common)
- Applications using RegExp patterns without stateful modifiers&lt;/p&gt;
&lt;p&gt;### Assessment Guide
To determine if you&amp;#39;re affected:&lt;/p&gt;
&lt;p&gt;Check if  allowedAud, allowedIss, allowedSub, allowedJti, or allowedNonce options use RegExp objects (/pattern/ or new RegExp())
If yes, review the pattern for stateful modifiers like /g, /y
If…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3j8v-cgw4-2g6q</guid>
    </item>
  </channel>
</rss>
