CVE-2025-61786: denoland deno · Improper Privilege Management
Affects denoland denoSource CVE Database V5
Not known to be exploited · CVSS 3.3 Low : upgrade to 2.2.15 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.2.15
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade denoland deno to 2.2.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| denoland deno | Affected
| Fixed in
|
AI-suggested
European organizations should immediately upgrade all Deno runtime instances to versions 2.5.3 or 2.2.15 or later to remediate this vulnerability. Review and audit permission configurations in Deno scripts to ensure the principle of least privilege is enforced. Avoid opening files with write-only flags if file metadata access is not required. Implement runtime monitoring to detect anomalous use of file stat APIs. In environments where upgrading is delayed, consider restricting execution of untrusted or third-party Deno scripts and isolate Deno workloads to minimize potential impact. Incorporate this vulnerability into vulnerability management and patching workflows, and educate developers on secure use of Deno’s permission model.
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.
References
- github.com/denoland/deno/security/advisories/GHSA-qq26-84mh-26j9 (opens in a new tab)
- github.com/denoland/deno/pull/30876 (opens in a new tab)
- github.com/denoland/deno/commit/1ab2268c0bcbf9b0468e0e36963f77f8c31c73ec (opens in a new tab)
- github.com/denoland/deno/releases/tag/v2.2.15 (opens in a new tab)
- github.com/denoland/deno/releases/tag/v2.5.3 (opens in a new tab)