Vulnerability in Deno (CVE-2025-61785)
Summary
Vulnerability in Deno (CVE-2025-61785). Risk of unauthorized operations or information disclosure. Exploitable via Deno.FsFile.prototype.utime.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-61785 has been found in Deno.
Attackers can target a specific entry point like Deno.FsFile.prototype.utime over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Deno CVE-2025-61785" on the vendor's site.
CVE-2025-61785 (Deno) — CWE-266 / CVSS v3 3.3
Attack vector: local / no user interaction
Attack surface: Deno.FsFile.prototype.utime / Deno.FsFile.prototype.utimeSync / atime / mtime
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-266) exists in Deno. Attackers reach the vulnerable code path via Deno.FsFile.prototype.utime.
Check the vendor advisory for the affected versions of Deno. Attack surface: Deno.FsFile.prototype.utime / Deno.FsFile.prototype.utimeSync / atime / mtime.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Deno' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Deno' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Denoを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。