denoland Deno up to 2.2.14/2.5.2 privileges management

Summaryinfo

A vulnerability was found in denoland Deno up to 2.2.14/2.5.2 and classified as critical. The impacted element is the function Deno.FsFile.prototype.stat/Deno.FsFile.prototype.statSync. The manipulation results in privileges management. This vulnerability is identified as CVE-2025-61786. The attack is only possible with local access. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in denoland Deno up to 2.2.14/2.5.2. Affected is the function Deno.FsFile.prototype.stat/Deno.FsFile.prototype.statSync. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-61786 since 09/30/2025. The exploitability is told to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1068.

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 1ab2268c0bcbf9b0468e0e36963f77f8c31c73ec 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.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion