CVE-2026-9473
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePath traversal vulnerability in c-rick jimeng-mcp 1.10.0 allows remote attackers to access arbitrary files via manipulation of the filePath argument in multiple file-handling functions (getFileContent, uploadCoverFile, generateImage, generateVideo) in src/api.ts. The vulnerability exploits insufficient input validation on path traversal sequences like '../'.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify jimeng-mcp installation and versionRun 'npm list jimeng-mcp' or check package.json to confirm jimeng-mcp is installed and note its version numberAffected if The installed version is exactly v1.10.0 or falls within the v1.10.x range
-
Locate the vulnerable API fileCheck for the presence of src/api.ts in the jimeng-mcp installation directoryAffected if The file src/api.ts exists and contains the functions getFileContent, uploadCoverFile, generateImage, or generateVideo
-
Confirm API exposureReview the application's API server configuration to determine if endpoints calling the affected functions are exposed to network or remote accessAffected if The vulnerable functions are exposed via API endpoints accessible to remote users
-
Check for path traversal protectionInspect src/api.ts code to verify whether the filePath parameter in the affected functions includes sanitization logic that rejects '..' or '../' sequencesAffected if No input validation or sanitization on the filePath parameter is found, or the code allows path traversal sequences through
A user is affected if jimeng-mcp v1.10.x is installed, the vulnerable API file exists with the affected functions, those functions are network-accessible, and no input validation blocks path traversal sequences in the filePath parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and path sanitization on the filePath parameter, using path resolution functions to canonicalize paths and reject requests containing traversal sequences or attempting to access files outside allowed directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9473 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data