CVE-2025-61787
A public proof of concept exists; no exploitation attested.
- Published2025-10-08
- Fixed in2.5.3
- WeaknessCWE-77
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions prior to 2.5.3 and 2.2.15 are vulnerable to Command Line Injection attacks on Windows when batch files are executed. In Windows, ``CreateProcess()`` always implicitly spawns ``cmd.exe`` if a batch file (.bat, .cmd, etc.) is being executed even if the application does not specify it via the command line. This makes Deno vulnerable to a command injection attack on Windows. Versions 2.5.3 and 2.2.15 fix the issue.
Timeline
dates in UTC- 2025-10-0802:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.x | ≥ 2.3.0, < 2.5.3 | 2.5.3 | NVD |
| 2.2 | ≤ 2.2.15 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.5 | < 2.5.2 | 2.5.2 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- denoland denoAffected
- = >= 2.3.0, < 2.5.3no fix stated
- = < 2.2.15no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-10-08
Fix
- Update Deno to 2.5.3
Advisories and patches
- github.comPatch
- github.comPatch
- github.comRelease Notes
- github.comRelease Notes
- github.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2025-10-08
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionpoc2025-10-08
- CNACVSS 3.18.1known since 2026-10-23
- CNAweakness (CWE)CWE-77known since 2026-10-23
- FIRST EPSSEPSS score2.1 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2025-10-08
Identifiers
- EUVD-2025-33179same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-m2gf-x3f6-8hq3same flawGitHub Advisory Database · CC-BY-4.0
- JLSEC-2026-113same flawJulia Security Advisories · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2025-10-08
- Last Modified
- 2026-10-08
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-m2gf-x3f6-8hq3
Frequently asked questions
What is CVE-2025-61787?
Is CVE-2025-61787 actively exploited?
What is the CVSS score for CVE-2025-61787?
Running deno? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-m2gf-x3f6-8hq3
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0