<?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>Wed, 07 Oct 2026 19:59:53 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-243015</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-243015</link>
      <description>EUVD-2026-243015</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-243015</guid>
    </item>
    <item>
      <title>fkie_cve-2025-48934</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-48934</link>
      <description>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to versions 2.1.13 and 2.2.13, the `Deno.env.toObject` method ignores any variables listed in the `--deny-env` option of the `deno run` command. When looking at the documentation of the `--deny-env` option this might lead to a false impression that variables listed in the option are impossible to read. Software relying on the combination of both flags to allow access to most environment variables except a few sensitive ones will be vulnerable to malicious code trying to steal secrets using the `Deno.env.toObject()` method. Versions 2.1.13 and 2.2.13 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to versions 2.1.13 and 2.2.13, the `Deno.env.toObject` method ignores any variables listed in the `--deny-env` option of the `deno run` command. When looking at the documentation of the `--deny-env` option this might lead to a false impression that variables listed in the option are impossible to read. Software relying on the combination of both flags to allow access to most environment variables except a few sensitive ones will be vulnerable to malicious code trying to steal secrets using the `Deno.env.toObject()` method. Versions 2.1.13 and 2.2.13 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-48934</guid>
    </item>
    <item>
      <title>GHSA-7w8p-chxq-2789 — Deno.env.toObject() ignores the variables listed in --deny-env and returns all environment variables</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7w8p-chxq-2789</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
The [Deno.env.toObject](https://docs.deno.com/api/deno/~/Deno.Env.toObject) method ignores any variables listed in the `--deny-env` option of the `deno run` command. When looking at the [documentation](https://docs.deno.com/runtime/fundamentals/security/#environment-variables) of the `--deny-env` option this might lead to a false impression that variables listed in the option are impossible to read.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```
export AWS_SECRET_ACCESS_KEY=my-secret-aws-key&lt;/p&gt;
&lt;p&gt;# Works as expected. The program stops with a &amp;#34;NotCapable&amp;#34; error message
echo &amp;#39;console.log(Deno.env.get(&amp;#34;AWS_SECRET_ACCESS_KEY&amp;#34;));&amp;#39; | deno run \
  --allow-env \
  --deny-env=AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY -&lt;/p&gt;
&lt;p&gt;# All enviroment variables are printed and the --deny-env list is completely disregarded
echo &amp;#39;console.log(Deno.env.toObject());&amp;#39; | deno run \
  --allow-env \
  --deny-env=AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY -
```&lt;/p&gt;
&lt;p&gt;The first example using `get` exits with the following error:
```
error: Uncaught (in promise) NotCapable: Requires env access to &amp;#34;AWS_SECRET_ACCESS_KEY&amp;#34;, run again with the --allow-env flag
console.log(Deno.env.get(&amp;#34;AWS_SECRET_ACCESS_KEY&amp;#34;));
                     ^
    at Object.getEnv [as get] (ext:deno_os/30_os.js:124:10)
    at file:///$deno$stdin.mts:1:22
```&lt;/p&gt;
&lt;p&gt;The second example  using `toObject` prints all environment variables:
```
[Object: null prototype] {
  ...
  AWS_SECRET_ACCESS_KEY: &amp;#34;my-secret-aws-key&amp;#34;,
  ...
}
```&lt;/p&gt;
&lt;p&gt;### Impact
Software relying on the combination of bo…&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
The [Deno.env.toObject](https://docs.deno.com/api/deno/~/Deno.Env.toObject) method ignores any variables listed in the `--deny-env` option of the `deno run` command. When looking at the [documentation](https://docs.deno.com/runtime/fundamentals/security/#environment-variables) of the `--deny-env` option this might lead to a false impression that variables listed in the option are impossible to read.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```
export AWS_SECRET_ACCESS_KEY=my-secret-aws-key&lt;/p&gt;
&lt;p&gt;# Works as expected. The program stops with a &amp;#34;NotCapable&amp;#34; error message
echo &amp;#39;console.log(Deno.env.get(&amp;#34;AWS_SECRET_ACCESS_KEY&amp;#34;));&amp;#39; | deno run \
  --allow-env \
  --deny-env=AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY -&lt;/p&gt;
&lt;p&gt;# All enviroment variables are printed and the --deny-env list is completely disregarded
echo &amp;#39;console.log(Deno.env.toObject());&amp;#39; | deno run \
  --allow-env \
  --deny-env=AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY -
```&lt;/p&gt;
&lt;p&gt;The first example using `get` exits with the following error:
```
error: Uncaught (in promise) NotCapable: Requires env access to &amp;#34;AWS_SECRET_ACCESS_KEY&amp;#34;, run again with the --allow-env flag
console.log(Deno.env.get(&amp;#34;AWS_SECRET_ACCESS_KEY&amp;#34;));
                     ^
    at Object.getEnv [as get] (ext:deno_os/30_os.js:124:10)
    at file:///$deno$stdin.mts:1:22
```&lt;/p&gt;
&lt;p&gt;The second example  using `toObject` prints all environment variables:
```
[Object: null prototype] {
  ...
  AWS_SECRET_ACCESS_KEY: &amp;#34;my-secret-aws-key&amp;#34;,
  ...
}
```&lt;/p&gt;
&lt;p&gt;### Impact
Software relying on the combination of bo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7w8p-chxq-2789</guid>
    </item>
  </channel>
</rss>
