<?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 07:43:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329635</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329635</link>
      <description>EUVD-2026-329635</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329635</guid>
    </item>
    <item>
      <title>fkie_cve-2026-49860</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49860</link>
      <description>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.1, when a WebSocket connection was opened, Deno checked the destination hostname against --deny-net rules but did not re-check the IP addresses that hostname resolved to. An attacker-controlled script could use a specially crafted domain name that passes the hostname check yet resolves to a denied IP, bypassing the network restriction entirely. This vulnerability is fixed in 2.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.1, when a WebSocket connection was opened, Deno checked the destination hostname against --deny-net rules but did not re-check the IP addresses that hostname resolved to. An attacker-controlled script could use a specially crafted domain name that passes the hostname check yet resolves to a denied IP, bypassing the network restriction entirely. This vulnerability is fixed in 2.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-49860</guid>
    </item>
    <item>
      <title>GHSA-83pc-3rw9-qpwj — Deno: WebSocket API sandbox bypass via missing post-DNS check</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-83pc-3rw9-qpwj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a WebSocket connection was opened, Deno checked the destination hostname
against `--deny-net` rules but did not re-check the IP addresses that hostname
resolved to. An attacker-controlled script could use a specially crafted domain
name that passes the hostname check yet resolves to a denied IP, bypassing the
network restriction entirely.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Code running under `--deny-net` could connect to hosts that the user intended
to block. In practice this means network isolation rules — for example,
blocking access to `localhost` or internal services — could be silently
circumvented by a malicious or compromised dependency.&lt;/p&gt;
&lt;p&gt;`Deno.connect` and `fetch()` were not affected by this specific issue (a
companion advisory covers `fetch()`).&lt;/p&gt;
&lt;p&gt;## Who is affected&lt;/p&gt;
&lt;p&gt;Users who:&lt;/p&gt;
&lt;p&gt;- run untrusted or third-party code with `deno run`, and
- rely on `--deny-net` to restrict which hosts that code can reach.&lt;/p&gt;
&lt;p&gt;If you do not use `--deny-net`, or if you only run fully trusted code, you are
not affected.&lt;/p&gt;
&lt;p&gt;## Workaround&lt;/p&gt;
&lt;p&gt;No workaround is available short of upgrading. If upgrading immediately is not
possible, avoid granting `--allow-net` to untrusted code that also has
`--deny-net` restrictions you depend on for security.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a WebSocket connection was opened, Deno checked the destination hostname
against `--deny-net` rules but did not re-check the IP addresses that hostname
resolved to. An attacker-controlled script could use a specially crafted domain
name that passes the hostname check yet resolves to a denied IP, bypassing the
network restriction entirely.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Code running under `--deny-net` could connect to hosts that the user intended
to block. In practice this means network isolation rules — for example,
blocking access to `localhost` or internal services — could be silently
circumvented by a malicious or compromised dependency.&lt;/p&gt;
&lt;p&gt;`Deno.connect` and `fetch()` were not affected by this specific issue (a
companion advisory covers `fetch()`).&lt;/p&gt;
&lt;p&gt;## Who is affected&lt;/p&gt;
&lt;p&gt;Users who:&lt;/p&gt;
&lt;p&gt;- run untrusted or third-party code with `deno run`, and
- rely on `--deny-net` to restrict which hosts that code can reach.&lt;/p&gt;
&lt;p&gt;If you do not use `--deny-net`, or if you only run fully trusted code, you are
not affected.&lt;/p&gt;
&lt;p&gt;## Workaround&lt;/p&gt;
&lt;p&gt;No workaround is available short of upgrading. If upgrading immediately is not
possible, avoid granting `--allow-net` to untrusted code that also has
`--deny-net` restrictions you depend on for security.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-83pc-3rw9-qpwj</guid>
    </item>
  </channel>
</rss>
