EUVD-2026-31706
GHSA-rf4q-8q48-538j
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability has been found in c-rick jimeng-mcp 1.10.0. Affected by this vulnerability is the function getFileContent/uploadCoverFile/generateImage/generateVideo of the file src/api.ts. The manipulation of the argument filePath leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
Path traversal in jimeng-mcp 1.10.0 allows low-privileged remote attackers to read and write files outside the intended directory by supplying crafted filePath arguments to four distinct API functions: getFileContent, uploadCoverFile, generateImage, and generateVideo in src/api.ts. A publicly available proof-of-concept exploit exists, disclosed via GitHub issue #15, though EPSS at 0.04% (13th percentile) indicates minimal observed mass-exploitation activity to date. No patch has been released and the vendor has not responded to the responsible disclosure, leaving deployments without an official remediation path.
Technical ContextAI
jimeng-mcp is a Model Context Protocol (MCP) server (CPE: cpe:2.3:a:c-rick:jimeng-mcp:*:*:*:*:*:*:*:*) that interfaces with AI-driven image and video generation services, exposing file system operations through its API layer. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory - Path Traversal): the filePath parameter accepted by the four functions in src/api.ts is not validated or canonicalized before being used in file system operations, allowing directory traversal sequences such as ../../ to escape the intended working directory. The breadth of the flaw - spanning four separate API functions handling different media workflows - indicates a systemic absence of input sanitization at the API layer rather than an isolated oversight.
RemediationAI
No vendor-released patch has been identified at time of analysis; the maintainer has not responded to the disclosure submitted via GitHub issue #15 (https://github.com/c-rick/jimeng-mcp/issues/15). As an immediate compensating control, organizations should restrict API access to the jimeng-mcp service exclusively to trusted, authenticated internal users and block any external network exposure - noting this reduces attack surface but does not eliminate the path traversal itself for insider threat scenarios. A direct mitigation is to fork the repository and manually patch src/api.ts to canonicalize and validate the filePath argument in getFileContent, uploadCoverFile, generateImage, and generateVideo, ensuring all resolved paths remain within an explicitly defined base directory before any file system operation is performed. Running the jimeng-mcp process in a containerized or chroot-jailed environment limits the file system scope accessible via traversal, reducing impact to files within the container boundary. File access monitoring for traversal patterns (sequences containing ../) can provide detection capability in the interim. References: https://vuldb.com/vuln/365454, https://github.com/c-rick/jimeng-mcp/issues/15.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today