CVE
Obot command injection in Docker MCP server file setup
- Exploited
- No known exploitation
- Fix
- Fixed in 0.27.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.27.0.
Summary
Obot, from obot-platform, has a command injection flaw in how it handles file-type MCP server configuration values during Docker MCP Server setup. A remote attacker with a low-privilege user account can run shell commands, modify the MCP server files volume, and reach services on Obot's Docker network.
Original description
Obot from 0.9.0 before 0.27.0 contains a command injection vulnerability that allows authenticated users to execute shell commands by embedding an EOF line in file-type MCP server configuration values. Attackers can terminate the heredoc in the generated init container script to run commands, modify the MCP server files volume, and reach services on Obot's Docker network.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Go packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.27.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130767 (Obot 0.9.0 before 0.27.0 Command Injection via Docker MCP Server File Setup), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130767 (entry last updated 2026-11-18):
Affected:
- Go package github.com/obot-platform/obot: from 0.9.0, fixed in 0.27.0
Fixed versions: 0.27.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130767 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130767 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/obot-platform/obot/security/advisories/GHSA-2mfp-9vv3-q737
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130767
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130767"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
From 0.9.0 · fixed in 0.27.0
Fixed in v0.27.0 (released Oct 20, 2026, 29 days before disclosure).
The latest release, v0.28.1, is not affected.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · obot-platform/obot · Advisory GHSA-2mfp-9vv3-q737 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130767 |
| Record | NVD · CVE-2026-130767 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130767
Is CVE-2026-130767 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-130767?
github.com/obot-platform/obot (Go): from 0.9.0 before 0.27.0.Source: cve.now feed data
How do I fix CVE-2026-130767?
Upgrade to a fixed version: 0.27.0.Source: cve.now feed data