# CVE-2025-59341: Local File Inclusion in esm.sh

> Attackers can exploit URL handling flaws in the esm.sh CDN to read arbitrary files from the host filesystem.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-49pv-gwxp-532r, GO-2025-3962

## What is CVE-2025-59341?

CVE-2025-59341 is a high-severity path traversal vulnerability in esm-dev esm.sh, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

esm.sh is a nobuild content delivery network(CDN) for modern web development. In 136 and earlier, a Local File Inclusion (LFI) issue was identified in the esm.sh service URL handling. An attacker could craft a request that causes the server to read and return files from the host filesystem (or other unintended file sources).

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-59341?

3 open source packages ship an affected version, including github.com/esm-dev/esm.sh.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/esm-dev/esm.sh` | Go | All versions | None |
| `github.com/esm-dev/esm.sh` | Go | All versions to 136 | None |
| `github.com/esm-dev/esm.sh` | Go | All versions to 136 | None |

## How do I fix CVE-2025-59341?

Upgrade to a fixed version.

## Is CVE-2025-59341 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59341 exists.

Public exploit code:

- esm.sh <= v136 - Local File Inclusion (nuclei): http/cves/2025/CVE-2025-59341.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59341 and fix it if it is affected.

What it is: CVE-2025-59341 is a high-severity path traversal vulnerability in esm-dev esm.sh, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59341 exists.

Affected packages and fixed versions:
- github.com/esm-dev/esm.sh (Go): affected all versions; no fix listed
- github.com/esm-dev/esm.sh (Go): affected all versions up to 136; no fix listed
- github.com/esm-dev/esm.sh (Go): affected all versions up to 136; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59341/ (Markdown: https://insights.sbomify.com/CVE-2025-59341/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59341
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59341
- OSV: https://osv.dev/vulnerability/CVE-2025-59341

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59341/
Summaries are generated and may contain mistakes; the official description above is the record.