CVE-2025-65025: github.com/esm-dev/esm.sh · esm.sh CDN service has arbitrary file write via tarslip
Affects github.com/esm-dev/esm.shSource GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 0.0.0-20251117232647-9d77b88c3207 soon.
Data as of 19 Nov 2026, 02:50 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.2 |
|---|
- Patch
- Available – fixed in 0.0.0-20251117232647-9d77b88c3207
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
Upgrade github.com/esm-dev/esm.sh to 0.0.0-20251117232647-9d77b88c3207.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/esm-dev/esm.sh | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in esm.sh version 0.0.0-20251117232647-9d77b88c3207 that fixes the path traversal vulnerability by properly validating extracted file paths. Users and administrators should upgrade to this fixed version to mitigate the risk. Until patched, avoid using untrusted registries via the 'X-Npmrc' header to prevent exploitation.
Description
esm.sh CDN service suffers from a Path Traversal vulnerability (CWE-22) during NPM package tarball extraction. An attacker can craft a malicious package with file paths containing '../' sequences, which allows writing files outside the intended extraction directory on the server. This is possible because esm.sh uses path.Join without validating the normalized path, enabling escape from the package directory. The vulnerability can be triggered by setting the 'X-Npmrc' header to an attacker-controlled registry, bypassing restrictions on official registries. A proof-of-concept demonstrates creating a tarball that writes a file to /tmp on the server. A fix is available in version 0.0.0-20251117232647-9d77b88c3207.