Unauthenticated file write via legacy route traversal
Published May 28, 2026 · Updated May 28, 2026
Path traversal in esm.sh before 137_3 allows remote attackers to write attacker-controlled data to arbitrary server paths. The legacy router concatenates unsanitized request-path components into a buildStorage.Put key, letting filesystem normalization resolve relative segments outside storage. Network access to a legacy route is sufficient; writes inherit the server process's permissions, and code execution requires overwriting an executed binary or script.
Summary
What happened
Path traversal in esm.sh before 137_3 allows remote attackers to write attacker-controlled data to arbitrary server paths. The legacy router concatenates unsanitized request-path components into a buildStorage.Put key, letting filesystem normalization resolve relative segments outside storage. Network access to a legacy route is sufficient; writes inherit the server process's permissions, and code execution requires overwriting an executed binary or script.
The record
- CVE
- CVE-2026-44593
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- esm-dev
- Product
- esm.sh
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 137
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA legacy-route traversal request exampleproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo