What’s Vulnerable › Vulnerabilities

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

• Severity: low (CVSS 3.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2025-10-08 · updated 2026-10-08
• Weakness: CWE-269

Description

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.

Affected products

• denoland deno: through 2.2.15; from 2.3.0 before 2.5.3 — fixed in 2.5.3

How to fix

Upgrade to a fixed version: denoland deno 2.5.3. Check the vendor advisory for mitigations.

References

• https://github.com/denoland/deno/commit/1ab2268c0bcbf9b0468e0e36963f77f8c31c73ec
• https://github.com/denoland/deno/pull/30876
• https://github.com/denoland/deno/releases/tag/v2.2.15
• https://github.com/denoland/deno/releases/tag/v2.5.3
• https://github.com/denoland/deno/security/advisories/GHSA-qq26-84mh-26j9

Get alerted when CVE-2025-61786 or the next vulnerability affects your stack