Description
Mockoon provides way to design and run mock APIs. Prior to 9.7.0, a FILE response whose filePath embeds request data is confined by getSafeFilePath in packages/commons-server/src/libs/server/server.ts with resolvedPath.startsWith(staticBaseDir). That prefix test has no path-separator boundary, so a ../-escaped path whose absolute form string-prefixes the base directory passes, allowing an unauthenticated client to read files from sibling paths outside the served directory through HTTP sendFile, WebSocket, or callbacks. This issue is fixed in version 9.7.0.
References6
- github.com/mockoon/mockoon/commit/b42bdfb7f82e83f0e81bea8e6fe41…
- github.com/mockoon/mockoon/pull/2255
- github.com/mockoon/mockoon/releases/tag/v9.7.0
- github.com/mockoon/mockoon/security/advisories/GHSA-8wqc-v2q8-v…
- mockoon.com/releases/9.7.0
- github.com/mockoon/mockoon/security/advisories/GHSA-8wqc-v2q8-v…
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 42 · as of 15 November 2026
- CWE
- CWE-22CWE-23
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.