<?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>Wed, 07 Oct 2026 15:21:34 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-318076</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-318076</link>
      <description>EUVD-2026-318076</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-318076</guid>
    </item>
    <item>
      <title>fkie_cve-2026-35039</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35039</link>
      <description>&lt;p&gt;fast-jwt provides fast JSON Web Token (JWT) implementation. From 0.0.1 to before 6.2.0, setting up a custom cacheKeyBuilder method which does not properly create unique keys for different tokens can lead to cache collisions. This could cause tokens to be mis-identified during the verification process leading to valid tokens returning claims from different valid tokens and users being mis-identified as other users based on the wrong token. Version 6.2.0 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fast-jwt provides fast JSON Web Token (JWT) implementation. From 0.0.1 to before 6.2.0, setting up a custom cacheKeyBuilder method which does not properly create unique keys for different tokens can lead to cache collisions. This could cause tokens to be mis-identified during the verification process leading to valid tokens returning claims from different valid tokens and users being mis-identified as other users based on the wrong token. Version 6.2.0 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-35039</guid>
    </item>
    <item>
      <title>GHSA-rp9m-7r4c-75qg — fast-jwt: Cache Confusion via cacheKeyBuilder Collisions Can Return Claims From a Different Token (Identity/Authorizati…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rp9m-7r4c-75qg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fast-jwt&lt;/p&gt;
&lt;p&gt;_NOTE_: While the library exposes a mechanism which could introduce the vulnerability, this issue is created by developer-supplied code and not by the library itself. We will add a warning and some education for users around the possible issues however since the defaults work we will not be updating the library beyond that for this advisory.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Setting up a custom cacheKeyBuilder method which does not properly create unique keys for different tokens can lead to cache collisions. This could cause tokens to be mis-identified during the verification process leading to:&lt;/p&gt;
&lt;p&gt;- Valid tokens returning claims from different valid tokens
- Users being mis-identified as other users based on the wrong token&lt;/p&gt;
&lt;p&gt;This could result in:
- User impersonation - UserB receives UserA&amp;#39;s identity and permissions
- Privilege escalation - Low-privilege users inherit admin-level access
- Cross-tenant data access - Users gain access to other tenants&amp;#39; resources
- Authorization bypass - Security decisions made on wrong user identity&lt;/p&gt;
&lt;p&gt;## Affected Configurations&lt;/p&gt;
&lt;p&gt;This vulnerability ONLY affects applications that BOTH:&lt;/p&gt;
&lt;p&gt;1. Enable caching using the cache option
2. Use custom cacheKeyBuilder functions that can produce collisions&lt;/p&gt;
&lt;p&gt;VULNERABLE examples:
```
// Collision-prone: same audience = same cache key
cacheKeyBuilder: (token) =&amp;gt; {
  const { aud } = parseToken(token)
  return `aud=${aud}`
}&lt;/p&gt;
&lt;p&gt;// Collision-prone: grouping by user type
cacheKeyBuilder: (token) =&amp;gt; {
  const { aud } = parseToken(token)
  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;_NOTE_: While the library exposes a mechanism which could introduce the vulnerability, this issue is created by developer-supplied code and not by the library itself. We will add a warning and some education for users around the possible issues however since the defaults work we will not be updating the library beyond that for this advisory.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Setting up a custom cacheKeyBuilder method which does not properly create unique keys for different tokens can lead to cache collisions. This could cause tokens to be mis-identified during the verification process leading to:&lt;/p&gt;
&lt;p&gt;- Valid tokens returning claims from different valid tokens
- Users being mis-identified as other users based on the wrong token&lt;/p&gt;
&lt;p&gt;This could result in:
- User impersonation - UserB receives UserA&amp;#39;s identity and permissions
- Privilege escalation - Low-privilege users inherit admin-level access
- Cross-tenant data access - Users gain access to other tenants&amp;#39; resources
- Authorization bypass - Security decisions made on wrong user identity&lt;/p&gt;
&lt;p&gt;## Affected Configurations&lt;/p&gt;
&lt;p&gt;This vulnerability ONLY affects applications that BOTH:&lt;/p&gt;
&lt;p&gt;1. Enable caching using the cache option
2. Use custom cacheKeyBuilder functions that can produce collisions&lt;/p&gt;
&lt;p&gt;VULNERABLE examples:
```
// Collision-prone: same audience = same cache key
cacheKeyBuilder: (token) =&amp;gt; {
  const { aud } = parseToken(token)
  return `aud=${aud}`
}&lt;/p&gt;
&lt;p&gt;// Collision-prone: grouping by user type
cacheKeyBuilder: (token) =&amp;gt; {
  const { aud } = parseToken(token)
  r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rp9m-7r4c-75qg</guid>
    </item>
  </channel>
</rss>
