Privilege escalation in Deno
CVE-2025-61785
Deno is a JavaScript, TypeScript, and WebAssembly runtime. In versions prior to 2.5.3 and 2.2.15, `Deno.FsFile.prototype.utime` and `Deno.FsFile.prototype.utimeSync` are not limited by the permission model check `--deny-write=./`. It's possible to change to change the access (`atime`) and modification (`mtime`) times on the file stream resource even when the file is opened with `read` only permission (and `write`: `false`) and file write operations are not allowed (the script is executed with `--deny-write=./`). Similar APIs like `Deno.utime` and `Deno.utimeSync` require `allow-write` permission, however, when a file is opened, even with read only flags and deny-write permission, it's still possible to change the access (`atime`) and modification (`mtime`) times, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 3.3 (Low). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.002, 10.5th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Deno
- Denoland Deno — versions >= 2.3.0, < 2.5.3, < 2.2.15
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (dellalibera/dellalibera, fkie-cad/nvd-json-data-feeds). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/denoland/deno/security/advisories/GHSA-vg2r-rmgp-cgqj (Exploit, Vendor Advisory)
- https://github.com/denoland/deno/pull/30872 (Patch, Issue Tracking)
- https://github.com/denoland/deno/commit/992e998dfe436cdc9325232759af8be92f11739b (Patch)
- https://github.com/denoland/deno/releases/tag/v2.2.15 (Release Notes)
- https://github.com/denoland/deno/releases/tag/v2.5.3 (Release Notes)