<?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, 13 Oct 2026 05:51:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325679</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325679</link>
      <description>EUVD-2026-325679</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325679</guid>
    </item>
    <item>
      <title>fkie_cve-2023-48238</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-48238</link>
      <description>&lt;p&gt;joaquimserafim/json-web-token is a javascript library use to interact with JSON Web Tokens (JWT) which are a compact URL-safe means of representing claims to be transferred between two parties. Versions prior to 4.0.0 are vulnerable to a JWT algorithm confusion attack. On line 86 of the &amp;#39;index.js&amp;#39; file, the algorithm to use for verifying the signature of the JWT token is taken from the JWT token, which at that point is still unverified and thus shouldn&amp;#39;t be trusted. To exploit this vulnerability, an attacker needs to craft a malicious JWT token containing the HS256 algorithm, signed with the public RSA key of the victim application. This attack will only work against this library is the RS256 algorithm is in use, however it is a best practice to use that algorithm. Version 4.0.0 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;joaquimserafim/json-web-token is a javascript library use to interact with JSON Web Tokens (JWT) which are a compact URL-safe means of representing claims to be transferred between two parties. Versions prior to 4.0.0 are vulnerable to a JWT algorithm confusion attack. On line 86 of the &amp;#39;index.js&amp;#39; file, the algorithm to use for verifying the signature of the JWT token is taken from the JWT token, which at that point is still unverified and thus shouldn&amp;#39;t be trusted. To exploit this vulnerability, an attacker needs to craft a malicious JWT token containing the HS256 algorithm, signed with the public RSA key of the victim application. This attack will only work against this library is the RS256 algorithm is in use, however it is a best practice to use that algorithm. Version 4.0.0 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-48238</guid>
    </item>
    <item>
      <title>GHSA-4xw9-cx39-r355 — json-web-token library is vulnerable to a JWT algorithm confusion attack</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4xw9-cx39-r355</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: json-web-token&lt;/p&gt;
&lt;p&gt;### Summary
The json-web-token library is vulnerable to a JWT algorithm confusion attack.&lt;/p&gt;
&lt;p&gt;### Details
On line 86 of the &amp;#39;index.js&amp;#39; file, the algorithm to use for verifying the signature of the JWT token is taken from the JWT token, which at that point is still unverified and thus shouldn&amp;#39;t be trusted. To exploit this vulnerability, an attacker needs to craft a malicious JWT token containing the HS256 algorithm, signed with the public RSA key of the victim application. This attack will only work against this library is the RS256 algorithm is in use, however it is a best practice to use that algorithm.&lt;/p&gt;
&lt;p&gt;### PoC
Take a server running the following code:
```javascript
const express = require(&amp;#39;express&amp;#39;);
const jwt = require(&amp;#39;json-web-token&amp;#39;);
const fs = require(&amp;#39;fs&amp;#39;);
const path = require(&amp;#39;path&amp;#39;);&lt;/p&gt;
&lt;p&gt;const app = express();
const port = 3000;&lt;/p&gt;
&lt;p&gt;// Load the keys from the file
const publicKeyPath = path.join(__dirname, &amp;#39;public-key.pem&amp;#39;);
const publicKey = fs.readFileSync(publicKeyPath, &amp;#39;utf8&amp;#39;);
const privateKeyPath = path.join(__dirname, &amp;#39;private-key.pem&amp;#39;);
const privateKey = fs.readFileSync(privateKeyPath, &amp;#39;utf8&amp;#39;);&lt;/p&gt;
&lt;p&gt;app.use(express.json());&lt;/p&gt;
&lt;p&gt;// Endpoint to generate a JWT token with admin: False
app.get(&amp;#39;/generateToken&amp;#39;, async (req, res) =&amp;gt; {
  const payload = { admin: false, name: req.query.name };
  const token = await jwt.encode(privateKey, payload, &amp;#39;RS256&amp;#39;, function (err, token) {
    res.json({ token });
  });
});&lt;/p&gt;
&lt;p&gt;// Middleware to verify the JWT token
function verifyToken(req, r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: json-web-token&lt;/p&gt;
&lt;p&gt;### Summary
The json-web-token library is vulnerable to a JWT algorithm confusion attack.&lt;/p&gt;
&lt;p&gt;### Details
On line 86 of the &amp;#39;index.js&amp;#39; file, the algorithm to use for verifying the signature of the JWT token is taken from the JWT token, which at that point is still unverified and thus shouldn&amp;#39;t be trusted. To exploit this vulnerability, an attacker needs to craft a malicious JWT token containing the HS256 algorithm, signed with the public RSA key of the victim application. This attack will only work against this library is the RS256 algorithm is in use, however it is a best practice to use that algorithm.&lt;/p&gt;
&lt;p&gt;### PoC
Take a server running the following code:
```javascript
const express = require(&amp;#39;express&amp;#39;);
const jwt = require(&amp;#39;json-web-token&amp;#39;);
const fs = require(&amp;#39;fs&amp;#39;);
const path = require(&amp;#39;path&amp;#39;);&lt;/p&gt;
&lt;p&gt;const app = express();
const port = 3000;&lt;/p&gt;
&lt;p&gt;// Load the keys from the file
const publicKeyPath = path.join(__dirname, &amp;#39;public-key.pem&amp;#39;);
const publicKey = fs.readFileSync(publicKeyPath, &amp;#39;utf8&amp;#39;);
const privateKeyPath = path.join(__dirname, &amp;#39;private-key.pem&amp;#39;);
const privateKey = fs.readFileSync(privateKeyPath, &amp;#39;utf8&amp;#39;);&lt;/p&gt;
&lt;p&gt;app.use(express.json());&lt;/p&gt;
&lt;p&gt;// Endpoint to generate a JWT token with admin: False
app.get(&amp;#39;/generateToken&amp;#39;, async (req, res) =&amp;gt; {
  const payload = { admin: false, name: req.query.name };
  const token = await jwt.encode(privateKey, payload, &amp;#39;RS256&amp;#39;, function (err, token) {
    res.json({ token });
  });
});&lt;/p&gt;
&lt;p&gt;// Middleware to verify the JWT token
function verifyToken(req, r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4xw9-cx39-r355</guid>
    </item>
    <item>
      <title>gsd-2023-48238</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-48238</link>
      <description>gsd-2023-48238</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-48238</guid>
    </item>
  </channel>
</rss>
