Description
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.
Affected products
deno: deno
References5
- github.com/denoland/deno/security/advisories/GHSA-vg2r-rmgp-cgqj ExploitVendor Advisory
- github.com/denoland/deno/commit/992e998dfe436cdc9325232759af8be… Patch
- github.com/denoland/deno/pull/30872 Issue TrackingPatch
- github.com/denoland/deno/releases/tag/v2.2.15 Release Notes
- github.com/denoland/deno/releases/tag/v2.5.3 Release Notes
Metrics
- CVSS 3.1
-
3.3
LOW
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - EPSS — exploit probability
- 0% percentile: 10 · as of 9 November 2026
- CWE
- CWE-266
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.