Esm maintains a focused command-line shell application (esm.sh) that occupies a narrow but prominent niche in systems tooling, with its limited disclosure footprint centered on input-handling and code-generation weaknesses including path traversal, server-side request forgery, code injection, and cross-site scripting. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Esm over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2025-65026CRITICAL esm.sh is a nobuild content delivery network(CDN) for modern web development. Prior to version 136, The esm.sh CDN service contains a Template Literal Injection vulnerability (CWE- | Nov 19, 2025 | 9.6 | 30 | NO | NO |
CVE-2025-65025CRITICAL esm.sh is a nobuild content delivery network(CDN) for modern web development. Prior to version 136, the esm.sh CDN service is vulnerable to path traversal during NPM package tarbal | Nov 19, 2025 | 9.8 | 27 | NO | NO |
CVE-2026-27730HIGH esm.sh is a no-build content delivery network (CDN) for web development. Versions up to and including 137 have an SSRF vulnerability (CWE-918) in esm.sh’s `/http(s)` fetch route. T | Feb 25, 2026 | 7.5 | 26 | NO | NO |
CVE-2025-50180HIGH esm.sh is a no-build content delivery network (CDN) for web development. In version 136, esm.sh is vulnerable to a full-response SSRF, allowing an attacker to retrieve information | Feb 25, 2026 | 7.5 | 25 | NO | NO |
CVE-2026-23644HIGH esm.sh is a no-build content delivery network (CDN) for web development. Prior to Go pseeudoversion 0.0.0-20260116051925-c62ab83c589e, the software has a path traversal vulnerabili | Jan 18, 2026 | 7.5 | 25 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Esm.
Media articles that mention a CVE ID that affects a product developed by Esm — matched by CVE ID, not by vendor name.