CVE-2025-50180

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 from internal websites through the vulnerability. Version 137 fixes the vulnerability.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available🟡 PoC Available

Full-response SSRF in esm.sh · Advisory · esm-dev/esm.sh · GitHub

https://github.com/esm-dev/esm.sh/security/advisories/GHSA-3c9r-837r-qqm4
github_release Patch Available

v137

Patch available: esm-dev/esm.sh v137

https://github.com/esm-dev/esm.sh/releases/tag/v137
github_pr Patch Available

Fix SSRF

Patch available: esm-dev/esm.sh v137 (PR #1149 merged 2025-06-16)

https://github.com/esm-dev/esm.sh/pull/1149
github_commit Patch Available

commit 0593516c4cfa (esm-dev/esm.sh)

Patch available: esm-dev/esm.sh v137 (contains commit 0593516c4cfa)

https://github.com/esm-dev/esm.sh/commit/0593516c4cfab49ad3b4900416a8432ff2e23eb0
generic

esm.sh/server/router.go at f80ff8c8d58749e77fa964abde468fc61f8bd89e · esm-dev/esm.sh · GitHub

https://github.com/esm-dev/esm.sh/blob/f80ff8c8d58749e77fa964abde468fc61f8bd89e/server/router.go#L511
generic

esm.sh/internal/fetch/fetch.go at f80ff8c8d58749e77fa964abde468fc61f8bd89e · esm-dev/esm.sh · GitHub

https://github.com/esm-dev/esm.sh/blob/f80ff8c8d58749e77fa964abde468fc61f8bd89e/internal/fetch/fetch.go#L13

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/esm-dev/esm.sh—0.0.0-20250616164159-0593516c4cfa—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 15:42 UTCEPSS rescore
  2. 2026-09-19 13:33 UTCOSV refresh
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-17 19:29 UTCEPSS rescore
  6. 2026-09-16 14:07 UTCEPSS rescore
  7. 2026-09-16 05:14 UTCEPSS rescore
  8. 2026-09-13 16:46 UTCEPSS rescore
  9. 2026-09-12 15:00 UTCEPSS rescore
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-11 09:36 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 21:59 UTCEPSS rescore
  14. 2026-09-07 16:00 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 15:28 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-08-31 17:04 UTCOSV refresh
  21. 2026-08-30 19:16 UTCEPSS rescore
  22. 2026-08-30 01:21 UTCEPSS rescore
  23. 2026-08-28 21:40 UTCEPSS rescore
  24. 2026-08-27 14:24 UTCEPSS rescore
  25. 2026-08-26 14:45 UTCEPSS rescore
Show 40 more
  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-24 14:16 UTCEPSS rescore
  3. 2026-08-24 09:22 UTCEPSS rescore
  4. 2026-08-23 00:18 UTCEPSS rescore
  5. 2026-08-21 23:48 UTCEPSS rescore
  6. 2026-08-20 22:54 UTCEPSS rescore
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-18 13:47 UTCEPSS rescore
  9. 2026-08-17 13:46 UTCEPSS rescore
  10. 2026-08-16 14:55 UTCEPSS rescore
  11. 2026-08-16 02:13 UTCEPSS rescore
  12. 2026-08-15 01:29 UTCEPSS rescore
  13. 2026-08-14 09:01 UTCEG score recompute
  14. 2026-08-13 21:59 UTCEPSS rescore
  15. 2026-08-13 01:01 UTCEG score recompute
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 23:58 UTCEG score recompute
  18. 2026-08-11 13:41 UTCEPSS rescore
  19. 2026-08-11 06:23 UTCEG score recompute
  20. 2026-08-10 23:59 UTCEPSS rescore
  21. 2026-08-09 20:54 UTCEG score recompute
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 08:39 UTCEG score recompute
  24. 2026-08-08 16:36 UTCEPSS rescore
  25. 2026-08-07 20:43 UTCEG score recompute
  26. 2026-08-06 13:46 UTCEPSS rescore
  27. 2026-08-06 03:01 UTCEG score recompute
  28. 2026-08-05 19:16 UTCEPSS rescore
  29. 2026-08-04 15:09 UTCEPSS rescore
  30. 2026-08-04 10:37 UTCEPSS rescore
  31. 2026-08-04 05:52 UTCEG score recompute
  32. 2026-08-03 10:35 UTCEPSS rescore
  33. 2026-08-02 19:34 UTCEG score recompute
  34. 2026-08-02 02:26 UTCEPSS rescore
  35. 2026-08-01 04:15 UTCEPSS rescore
  36. 2026-07-30 16:27 UTCEPSS rescore
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-28 15:35 UTCEPSS rescore
  40. 2026-07-27 14:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-50180?
CVE-2025-50180 is a high vulnerability published on February 25, 2026. 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 from internal websites through the vulnerability. Version 137 fixes the vulnerability.
When was CVE-2025-50180 disclosed?
CVE-2025-50180 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-50180 actively exploited?
CVE-2025-50180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.0% of all scored CVEs.
What is the CVSS score of CVE-2025-50180?
CVE-2025-50180 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-50180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-50180, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-50180

Explore →

Is Your Infrastructure Affected by CVE-2025-50180?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs