CVE-2026-6130
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 flaw has been found in chatboxai chatbox up to 1.20.0. This impacts the function StdioClientTransport of the file src/main/mcp/ipc-stdio-transport.ts of the component Model Context Protocol Server Management System. Executing a manipulation of the argument args/env can lead to os command injection. The attack can be launched remotely. The exploit has been published 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 confidenceOS command injection vulnerability in ChatboxAI Chatbox up to v1.20.0 in the StdioClientTransport function within src/main/mcp/ipc-stdio-transport.ts allows remote attackers to execute arbitrary OS commands via manipulated args/env parameters.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if ChatboxAI Chatbox is installedLocate the Chatbox application installation directory or check installed packages using system package manager (e.g., `where chatbox`, `which chatbox`, or check in Programs files)Affected if ChatboxAI Chatbox is found on the system
-
Identify the installed version of ChatboxAI ChatboxRun the application with version flag (e.g., `chatbox --version` or `chatbox -v`) or check the application metadata/About dialogAffected if The version is 1.20.0 or lower (any version up to and including 1.20.0)
-
Locate the vulnerable source fileSearch for the file src/main/mcp/ipc-stdio-transport.ts within the Chatbox installation directory or source code repositoryAffected if The file exists and contains the StdioClientTransport function implementation
-
Check if StdioClientTransport is in useExamine application logs, configuration files, or running processes to determine if the StdioClientTransport (stdin/stdout IPC mechanism) is actively being used by the applicationAffected if StdioClientTransport is enabled and processing IPC communications
-
Verify exposure to untrusted inputReview application configuration, API endpoints, or any integration points that accept args/env parameters and pass them to the StdioClientTransport functionAffected if The application accepts or processes external args/env parameters without validation
A user is affected if ChatboxAI Chatbox version 1.20.0 or lower is installed AND the StdioClientTransport function processes untrusted args/env parameters.
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/sanitization for args and env parameters in the StdioClientTransport function, using allowlists or safe APIs instead of direct command execution. Until a vendor patch is available, restrict network access to the affected service.
- 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-6130 — 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-6130 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