# CVE-2023-26126: m.static Directory Traversal vulnerability

> Attackers can read arbitrary files from the server due to improper input sanitization in the m.static npm package.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-vcxh-qvgr-9fw9

## What is CVE-2023-26126?

CVE-2023-26126 is a high-severity path traversal vulnerability in m.static, published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the package m.static are vulnerable to Directory Traversal due to improper input sanitization of the path being requested via the requestFile function.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-26126?

2 open source packages ship an affected version, including m.static. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `m.static` | npm | All versions to 2.2.0 | None |
| `m.static` | npm | All versions to 2.2.0 | None |

Products: M.static Project M.static.

## How do I fix CVE-2023-26126?

No fix has been published for CVE-2023-26126 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-26126 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26126 and fix it if it is affected.

What it is: CVE-2023-26126 is a high-severity path traversal vulnerability in m.static, published on 10 May 2023. 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-2023-26126 exists.

Affected packages and fixed versions:
- m.static (npm): affected all versions up to 2.2.0; no fix listed
- m.static (npm): affected all versions up to 2.2.0; 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-2023-26126/ (Markdown: https://insights.sbomify.com/CVE-2023-26126/index.md)
```

## Sources

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

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