CVE-2026-5621
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 was found in ChrisChinchilla Vale-MCP up to 0.1.0. Affected by this vulnerability is an unknown functionality of the file src/index.ts of the component HTTP Interface. The manipulation of the argument config_path results in os command injection. Attacking locally is a requirement. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceCommand injection vulnerability in Vale-MCP (up to 0.1.0) allows execution of arbitrary OS commands through the config_path argument in the HTTP Interface component (src/index.ts). The vulnerability requires local access to exploit.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/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.
-
Confirm Vale-MCP is installedRun `npm list vale-mcp` or check for vale-mcp in your node_modules, or look for the vale-mcp executable/service in your environmentAffected if Vale-MCP is not present in the environment, the system is not affected
-
Identify the installed Vale-MCP versionRun `npm list vale-mcp` or `vale-mcp --version` to get the version number, then compare it to any official version releases of Vale-MCPAffected if The installed version has not received a fix for the command injection in src/index.ts
-
Verify the HTTP interface is enabledCheck your Vale-MCP configuration or startup flags for HTTP server settings (--http-port, --http-host, or similar HTTP-related flags in your config)Affected if The HTTP interface is enabled and accessible, making the config_path parameter reachable
-
Inspect src/index.ts for config_path handlingLocate the Vale-MCP source code in node_modules/vale-mcp/src/index.ts and search for 'config_path' to see how it is processed and whether it is sanitized before being used in command executionAffected if The code shows config_path is passed directly to a command execution function (such as exec, spawn, or shell) without sanitization or validation checks
-
Test for command injection vulnerabilityIf you have access to the HTTP interface, send a crafted request with a config_path value containing shell metacharacters (e.g., `config_path=file.txt;whoami`) and observe if the appended command executesAffected if The HTTP interface reflects the injected command in the response or executes the appended command, confirming the vulnerability is present
The environment is affected if Vale-MCP is running with its HTTP interface enabled and the config_path parameter can be manipulated to inject OS commands due to lack of sanitization in src/index.ts.
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 sanitization on the config_path parameter, preferably using allowlists or path normalization to prevent command injection. Avoid passing user-controlled input directly to OS command execution functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5621 — 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-5621 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