# CVE-2025-59049: Mockoon has a Path Traversal and LFI in the static file serving endpoint

> An attacker can exploit path traversal in Mockoon's static file serving to read arbitrary files from the server filesystem.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-w7f9-wqc4-3wxr

## What is CVE-2025-59049?

CVE-2025-59049 is a high-severity path traversal vulnerability in mockoon, published on 10 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mockoon provides way to design and run mock APIs. Prior to version 9.2.0, a mock API configuration for static file serving follows the same approach presented in the documentation page, where the server filename is generated via templating features from user input is vulnerable to Path Traversal and LFI, allowing an attacker to get any file in the mock server filesystem.
The issue may be particularly relevant in cloud hosted server instances. Version 9.2.0 fixes the issue.

Weakness: CWE-24 (Path Traversal: '../filedir'), CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

4 open source packages ship an affected version, including @mockoon/cli and @mockoon/commons-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@mockoon/cli` | npm | All versions | 9.2.0 |
| `@mockoon/cli` | npm | All versions | 9.2.0 |
| `@mockoon/commons-server` | npm | All versions | 9.2.0 |
| `@mockoon/commons-server` | npm | All versions | 9.2.0 |

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

Upgrade @mockoon/cli to 9.2.0 or later.

## Is CVE-2025-59049 being exploited?

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

Public exploit code:

- Mockoon < 9.2.0 - Path Traversal (nuclei): http/cves/2025/CVE-2025-59049.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59049 is a high-severity path traversal vulnerability in mockoon, published on 10 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-59049 exists.

Affected packages and fixed versions:
- @mockoon/cli (npm): affected all versions; fixed in 9.2.0
- @mockoon/cli (npm): affected all versions; fixed in 9.2.0
- @mockoon/commons-server (npm): affected all versions; fixed in 9.2.0
- @mockoon/commons-server (npm): affected all versions; fixed in 9.2.0

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-59049/ (Markdown: https://insights.sbomify.com/CVE-2025-59049/index.md)
```

## Sources

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

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