<?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 04:48:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-49406 — Deno: BYONM module resolution allows `package.json` main path traversal to bypass `--allow-read` restrictions</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-49406</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; denoland deno&lt;/p&gt;
&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.12, when Deno was run in BYONM mode (nodeModulesDir: &amp;#34;manual&amp;#34;), the module resolver did not validate that a package&amp;#39;s resolved entrypoint stayed within its node_modules/&amp;lt;pkg&amp;gt;/ directory. A malicious package.json whose main field contained .. segments was able to resolve to an arbitrary path on disk, and the resolver then read that file without consulting the --allow-read allowlist. This let a require(&amp;#34;evil-pkg&amp;#34;) call return the contents of a file that a direct Deno.readTextFileSync(...) call would have been blocked from reading. This vulnerability is fixed in 2.7.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; denoland deno&lt;/p&gt;
&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.12, when Deno was run in BYONM mode (nodeModulesDir: &amp;#34;manual&amp;#34;), the module resolver did not validate that a package&amp;#39;s resolved entrypoint stayed within its node_modules/&amp;lt;pkg&amp;gt;/ directory. A malicious package.json whose main field contained .. segments was able to resolve to an arbitrary path on disk, and the resolver then read that file without consulting the --allow-read allowlist. This let a require(&amp;#34;evil-pkg&amp;#34;) call return the contents of a file that a direct Deno.readTextFileSync(...) call would have been blocked from reading. This vulnerability is fixed in 2.7.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-49406</guid>
    </item>
  </channel>
</rss>
