Mockoon - Authentication Bypass (CVE-2026-59148)
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.
psychologyCrowdSec Analysis
CVE-2026-59148 is a high-severity authentication bypass in Mockoon versions before 9.7.0, exposing the unauthenticated admin API on the mock server’s listener. Attackers who can reach the server port may read sensitive environment variables and transaction data, modify process variables and mock API responses, or purge application state, potentially compromising confidentiality, integrity, and availability. Upgrade to Mockoon 9.7.0 or later to address the vulnerability.
CrowdSec has been tracking this vulnerability and its exploits since 18th of November 2026.
CrowdSec has not observed any significant exploitation activity targeting CVE-2026-59148 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.
Observed exploitation attempts target /mockoon-admin to access Mockoon’s unauthenticated admin API. Requests to this endpoint may indicate attempts to access administrative functionality without a bearer token.
Full Intelligence Available
Connect your API key to access CrowdSec scores, exploit timelines, and attacker IPs.
| Event | Date |
|---|---|
| CVE Published | 2026-07-09 |
| Rule Released | 2026-11-18 |
Related Weaknesses
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
Remediation & Protection
External References
- https://github.com/mockoon/mockoon/commit/c420b5a56918475b8663977b51e5f986e45b3299
- https://github.com/mockoon/mockoon/pull/2254
- https://github.com/mockoon/mockoon/releases/tag/v9.7.0
- https://mockoon.com/releases/9.7.0
- https://github.com/mockoon/mockoon/security/advisories/GHSA-rqx4-3f6q-3x2v
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-59148.yaml