<?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>Fri, 09 Oct 2026 14:03:42 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-243013</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-243013</link>
      <description>EUVD-2026-243013</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-243013</guid>
    </item>
    <item>
      <title>fkie_cve-2025-24015</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-24015</link>
      <description>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions 1.46.0 through 2.1.6 have an issue that affects AES-256-GCM and AES-128-GCM in Deno in which the authentication tag is not being validated. This means tampered ciphertexts or incorrect keys might not be detected, which breaks the guarantees expected from AES-GCM. Older versions of Deno correctly threw errors in such cases, as does Node.js. Without authentication tag verification, AES-GCM degrades to essentially CTR mode, removing integrity protection. Authenticated data set with set_aad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective. Version 2.1.7 includes a patch that addresses this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions 1.46.0 through 2.1.6 have an issue that affects AES-256-GCM and AES-128-GCM in Deno in which the authentication tag is not being validated. This means tampered ciphertexts or incorrect keys might not be detected, which breaks the guarantees expected from AES-GCM. Older versions of Deno correctly threw errors in such cases, as does Node.js. Without authentication tag verification, AES-GCM degrades to essentially CTR mode, removing integrity protection. Authenticated data set with set_aad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective. Version 2.1.7 includes a patch that addresses this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-24015</guid>
    </item>
    <item>
      <title>GHSA-2x3r-hwv5-p32x — Deno's AES GCM authentication tags are not verified</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2x3r-hwv5-p32x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno, crates.io: deno_node&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;This affects AES-256-GCM and AES-128-GCM in Deno, introduced by commit [0d1beed](https://github.com/denoland/deno/commit/0d1beed). Specifically, the authentication tag is not being validated. This means tampered ciphertexts or incorrect keys might not be detected, which breaks the guarantees expected from AES-GCM. Older versions of Deno correctly threw errors in such cases, as does Node.js.&lt;/p&gt;
&lt;p&gt;Without authentication tag verification, AES-GCM degrades to essentially CTR mode, removing integrity protection. Authenticated data set with set_aad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```ts
import { Buffer } from &amp;#34;node:buffer&amp;#34;;
import {
  createCipheriv,
  createDecipheriv,
  randomBytes,
  scrypt,
} from &amp;#34;node:crypto&amp;#34;;&lt;/p&gt;
&lt;p&gt;type Encrypted = {
  salt: string;
  iv: string;
  enc: string;
  authTag: string;
};&lt;/p&gt;
&lt;p&gt;const deriveKey = (key: string, salt: Buffer) =&amp;gt;
  new Promise&amp;lt;Buffer&amp;gt;((res, rej) =&amp;gt;
    scrypt(key, salt, 32, (err, k) =&amp;gt; {
      if (err) rej(err);
      else res(k);
    })
  );&lt;/p&gt;
&lt;p&gt;async function encrypt(text: string, key: string): Promise&amp;lt;Encrypted&amp;gt; {
  const salt = randomBytes(32);
  const k = await deriveKey(key, salt);&lt;/p&gt;
&lt;p&gt;const iv = randomBytes(16);
  const enc = createCipheriv(&amp;#34;aes-256-gcm&amp;#34;, k, iv);
  const ciphertext = enc.update(text, &amp;#34;binary&amp;#34;, &amp;#34;binary&amp;#34;) + enc.final(&amp;#34;binary&amp;#34;);&lt;/p&gt;
&lt;p&gt;return {
    salt: salt.toString(&amp;#34;binary&amp;#34;),
    iv: iv.toString(&amp;#34;binary&amp;#34;),
    en…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno, crates.io: deno_node&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;This affects AES-256-GCM and AES-128-GCM in Deno, introduced by commit [0d1beed](https://github.com/denoland/deno/commit/0d1beed). Specifically, the authentication tag is not being validated. This means tampered ciphertexts or incorrect keys might not be detected, which breaks the guarantees expected from AES-GCM. Older versions of Deno correctly threw errors in such cases, as does Node.js.&lt;/p&gt;
&lt;p&gt;Without authentication tag verification, AES-GCM degrades to essentially CTR mode, removing integrity protection. Authenticated data set with set_aad is also affected, as it is incorporated into the GCM hash (ghash) but this too is not validated, rendering AAD checks ineffective.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```ts
import { Buffer } from &amp;#34;node:buffer&amp;#34;;
import {
  createCipheriv,
  createDecipheriv,
  randomBytes,
  scrypt,
} from &amp;#34;node:crypto&amp;#34;;&lt;/p&gt;
&lt;p&gt;type Encrypted = {
  salt: string;
  iv: string;
  enc: string;
  authTag: string;
};&lt;/p&gt;
&lt;p&gt;const deriveKey = (key: string, salt: Buffer) =&amp;gt;
  new Promise&amp;lt;Buffer&amp;gt;((res, rej) =&amp;gt;
    scrypt(key, salt, 32, (err, k) =&amp;gt; {
      if (err) rej(err);
      else res(k);
    })
  );&lt;/p&gt;
&lt;p&gt;async function encrypt(text: string, key: string): Promise&amp;lt;Encrypted&amp;gt; {
  const salt = randomBytes(32);
  const k = await deriveKey(key, salt);&lt;/p&gt;
&lt;p&gt;const iv = randomBytes(16);
  const enc = createCipheriv(&amp;#34;aes-256-gcm&amp;#34;, k, iv);
  const ciphertext = enc.update(text, &amp;#34;binary&amp;#34;, &amp;#34;binary&amp;#34;) + enc.final(&amp;#34;binary&amp;#34;);&lt;/p&gt;
&lt;p&gt;return {
    salt: salt.toString(&amp;#34;binary&amp;#34;),
    iv: iv.toString(&amp;#34;binary&amp;#34;),
    en…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2x3r-hwv5-p32x</guid>
    </item>
  </channel>
</rss>
