# CVE-2026-59148: Mockoon: Unauthenticated admin API + wildcard CORS allows mock-state hijack and secret theft

> Unauthenticated access to Mockoon's admin API allows attackers to steal secrets and modify mock server state due to missing authentication and permissive CORS settings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-rqx4-3f6q-3x2v

## What is CVE-2026-59148?

CVE-2026-59148 is a high-severity missing authorization vulnerability in mockoon, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Mockoon provides way to design and run mock APIs. Prior to 9.7.0, Mockoon's admin API in commons-server/src/libs/server/admin-api.ts is mounted on the same Express listener as user-defined mock routes, enabled by default in shipped runtimes, serves Access-Control-Allow-Origin: * with write methods allowed, and has no authentication. Any unauthenticated caller who can reach the mock server port can read MOCKOON_* environment variables, write arbitrary process environment variables through /mockoon-admin/env-vars, rewrite mock route bodies, statuses, and headers through PUT /mockoon-admin/environment, read transaction logs and SSE streams, and purge state. This issue is fixed in version 9.7.0.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-352 (Cross-Site Request Forgery), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-59148?

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.7.0 |
| `@mockoon/cli` | npm | All versions | 9.7.0 |
| `@mockoon/commons-server` | npm | All versions | 9.7.0 |
| `@mockoon/commons-server` | npm | All versions | 9.7.0 |

## How do I fix CVE-2026-59148?

Upgrade @mockoon/cli to 9.7.0 or later.

## Is CVE-2026-59148 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59148 and fix it if it is affected.

What it is: CVE-2026-59148 is a high-severity missing authorization vulnerability in mockoon, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59148 exists.

Affected packages and fixed versions:
- @mockoon/cli (npm): affected all versions; fixed in 9.7.0
- @mockoon/cli (npm): affected all versions; fixed in 9.7.0
- @mockoon/commons-server (npm): affected all versions; fixed in 9.7.0
- @mockoon/commons-server (npm): affected all versions; fixed in 9.7.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-2026-59148/ (Markdown: https://insights.sbomify.com/CVE-2026-59148/index.md)
```

## Sources

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

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