denoland Deno up to 2.2.14/2.5.2 privileges assignment

Summaryinfo

A vulnerability has been found in denoland Deno up to 2.2.14/2.5.2 and classified as problematic. The affected element is the function Deno.FsFile.prototype.utime/Deno.FsFile.prototype.utimeSync. The manipulation leads to privileges assignment. This vulnerability is referenced as CVE-2025-61785. The attack can only be performed from a local environment. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in denoland Deno up to 2.2.14/2.5.2. This issue affects the function Deno.FsFile.prototype.utime/Deno.FsFile.prototype.utimeSync. The manipulation with an unknown input leads to a privileges assignment vulnerability. Using CWE to declare the problem leads to CWE-266. A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. Impacted is integrity. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-61785 since 09/30/2025. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 2.2.15 or 2.5.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 992e998dfe436cdc9325232759af8be92f11739b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202510-1203). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• denoland

Name

• Deno

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7
• 2.2.8
• 2.2.9
• 2.2.10
• 2.2.11
• 2.2.12
• 2.2.13
• 2.2.14
• 2.5.0
• 2.5.1
• 2.5.2

License

• open-source

Website

• Product: https://github.com/denoland/deno/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion