Skip to content
Fencer Intel
high 7.5

CVE-2025-59049 json

Mockoon has a Path Traversal and LFI in the static file serving endpoint

published last yr. modified 4mo ago also GHSA-w7f9-wqc4-3wxr , EUVD-2025-27607

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • npm @mockoon/commons-server 9.2.0
  • npm @mockoon/cli 9.2.0

Is CVE-2025-59049 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm @mockoon/commons-server
<9.2.0
9.2.0
npm @mockoon/cli
<9.2.0
9.2.0

Affected products

  • mockoon mockoon

Classification

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

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.