<?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 23:10:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-4424</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-4424</link>
      <description>EUVD-2026-4424</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-4424</guid>
    </item>
    <item>
      <title>fkie_cve-2024-27936</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-27936</link>
      <description>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime with secure defaults. Starting in version 1.32.1 and prior to version 1.41.0 of the deno library, maliciously crafted permission request can show the spoofed permission prompt by inserting a broken ANSI escape sequence into the request contents. Deno is stripping any ANSI escape sequences from the permission prompt, but permissions given to the program are based on the contents that contain the ANSI escape sequences. Any Deno program can spoof the content of the interactive permission prompt by inserting a broken ANSI code, which allows a malicious Deno program to display the wrong file path or program name to the user. Version 1.41.0 of the deno library contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime with secure defaults. Starting in version 1.32.1 and prior to version 1.41.0 of the deno library, maliciously crafted permission request can show the spoofed permission prompt by inserting a broken ANSI escape sequence into the request contents. Deno is stripping any ANSI escape sequences from the permission prompt, but permissions given to the program are based on the contents that contain the ANSI escape sequences. Any Deno program can spoof the content of the interactive permission prompt by inserting a broken ANSI code, which allows a malicious Deno program to display the wrong file path or program name to the user. Version 1.41.0 of the deno library contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-27936</guid>
    </item>
    <item>
      <title>GHSA-m4pq-fv2w-6hrw — Deno's deno_runtime vulnerable to interactive permission prompt spoofing via improper ANSI stripping</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m4pq-fv2w-6hrw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno, crates.io: deno_runtime&lt;/p&gt;
&lt;p&gt;### Summary
A maliciously crafted permission request can show the spoofed permission prompt by inserting a broken ANSI escape sequence into the request contents.&lt;/p&gt;
&lt;p&gt;### Details
In [the patch for CVE-2023-28446](https://github.com/denoland/deno/commit/78d430103a8f6931154ddbbe19d36f3b8630286d), Deno is stripping any ANSI escape sequences from the permission prompt, but permissions given to the program are based on the contents that contain the ANSI escape sequences.&lt;/p&gt;
&lt;p&gt;For example, requesting the read permission with `/tmp/hello\u001b[/../../etc/hosts` as a path will display the `/tmp/hellotc/hosts` in the permission prompt, but the actual permission given to the program is `/tmp/hello\u001b[/../../etc/hosts`, which is `/etc/hosts` after the normalization.&lt;/p&gt;
&lt;p&gt;This difference allows a malicious Deno program to spoof the contents of the permission prompt.&lt;/p&gt;
&lt;p&gt;### PoC
Run the following JavaScript and observe that `/tmp/hellotc/hosts` is displayed in the permission prompt instead of `/etc/hosts`, although Deno gives access to `/etc/hosts`.
``` javascript
const permission = { name: &amp;#34;read&amp;#34;, path: &amp;#34;/tmp/hello\u001b[/../../etc/hosts&amp;#34; };
await Deno.permissions.request(permission);
console.log(await Deno.readTextFile(&amp;#34;/etc/hosts&amp;#34;));
```&lt;/p&gt;
&lt;p&gt;#### Expected prompt
```
┌ ⚠️  Deno requests read access to &amp;#34;/etc/hosts&amp;#34;.
├ Requested by `Deno.permissions.query()` API
├ Run again with --allow-read to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all read permissions) &amp;gt;
```&lt;/p&gt;
&lt;p&gt;#…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno, crates.io: deno_runtime&lt;/p&gt;
&lt;p&gt;### Summary
A maliciously crafted permission request can show the spoofed permission prompt by inserting a broken ANSI escape sequence into the request contents.&lt;/p&gt;
&lt;p&gt;### Details
In [the patch for CVE-2023-28446](https://github.com/denoland/deno/commit/78d430103a8f6931154ddbbe19d36f3b8630286d), Deno is stripping any ANSI escape sequences from the permission prompt, but permissions given to the program are based on the contents that contain the ANSI escape sequences.&lt;/p&gt;
&lt;p&gt;For example, requesting the read permission with `/tmp/hello\u001b[/../../etc/hosts` as a path will display the `/tmp/hellotc/hosts` in the permission prompt, but the actual permission given to the program is `/tmp/hello\u001b[/../../etc/hosts`, which is `/etc/hosts` after the normalization.&lt;/p&gt;
&lt;p&gt;This difference allows a malicious Deno program to spoof the contents of the permission prompt.&lt;/p&gt;
&lt;p&gt;### PoC
Run the following JavaScript and observe that `/tmp/hellotc/hosts` is displayed in the permission prompt instead of `/etc/hosts`, although Deno gives access to `/etc/hosts`.
``` javascript
const permission = { name: &amp;#34;read&amp;#34;, path: &amp;#34;/tmp/hello\u001b[/../../etc/hosts&amp;#34; };
await Deno.permissions.request(permission);
console.log(await Deno.readTextFile(&amp;#34;/etc/hosts&amp;#34;));
```&lt;/p&gt;
&lt;p&gt;#### Expected prompt
```
┌ ⚠️  Deno requests read access to &amp;#34;/etc/hosts&amp;#34;.
├ Requested by `Deno.permissions.query()` API
├ Run again with --allow-read to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all read permissions) &amp;gt;
```&lt;/p&gt;
&lt;p&gt;#…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m4pq-fv2w-6hrw</guid>
    </item>
    <item>
      <title>gsd-2024-27936</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-27936</link>
      <description>gsd-2024-27936</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-27936</guid>
    </item>
  </channel>
</rss>
