Skip to content

AAK-DOCSGPT-MCP-STDIO-MITM-001: DocsGPT MCP transport-flip MITM (OX 2026-05-01, CVE-2026-26015 family)

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/docsgpt_transport_flip.py, agent_audit_kit/scanners/supply_chain.py
Auto-fixable
No.
SARIF name
DocsGptMcpTransportFlip

What it detects

Two-arm detector for the OX MCP 2026-05-01 disclosure batch. Arm 1 — pin-check on the npm docsgpt / docsgpt-mcp package, GitHub arc53/DocsGPT git refs in package.json / lockfiles, and the same package in pyproject.toml / requirements*.txt. Fires for any pin below the patched 0.6.4 floor. Arm 2 — server-config scanner that fires when a DocsGPT MCP config declares a safe transport (sse / http / https) but permits a post-handshake transport=stdio override (the MITM transport-flip path the disclosure traced through CVE-2026-26015). The architectural receiver-side class is already covered by AAK-MCP-STDIO-CMD-INJ-001/002/003/004 + AAK-STDIO-001 (shipped v0.3.6); this rule adds the product-named pin row consumers expect when grepping CHANGELOG.cves.md for 'DocsGPT' plus the transport-flip-resistance check the receiver-side rules don't catch.

How to fix

Pin DocsGPT >= 0.6.4 (the vendor fix from the OX 2026-05-01 batch). That version pin is the control that actually works today. For the transport-flip path itself, protect the channel rather than the config: serve the MCP endpoint over TLS with certificate verification enabled so a middlebox cannot rewrite the handshake, and prefer a client that pins the transport it negotiated. The receiver-side detectors (AAK-MCP-STDIO-CMD-INJ-*, AAK-STDIO-001) catch the downstream command injection if a flip does succeed. Note on deny_stdio_transport / allowed_transports: this rule treats those keys as a short-circuit, but they are AgentAuditKit conventions, not fields the MCP specification defines — they appear in none of the 748 public MCP configs in this project's corpus. Adding them silences this rule and is ignored by your MCP client, so do not treat their presence as protection.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-DOCSGPT-MCP-STDIO-MITM-001

Limitations

Two arms. The pin reads npm docsgpt and docsgpt-mcp in the root package.json, package-lock.json, yarn.lock and pnpm-lock.yaml, and the name followed directly by a version in the root requirements*.txt and pyproject.toml, and reports a version below 0.6.4 or any arc53/DocsGPT git reference. A node_modules/docsgpt entry that only a transitive dependency adds to package-lock.json, a version recorded only in uv.lock (name and version sit on separate lines), a sub-directory package.json and an arc53/docsgpt image tag in a compose file are not read. The config arm reads JSON MCP configs (.mcp.json, mcp.json, .cursor/mcp.json, .vscode/mcp.json), DocsGPT's own config files at the root and in .docsgpt/, and the .json files of a top-level configs/, and reports one that names DocsGPT, declares an sse, http, https or streamable-http transport and enables stdio explicitly (stdio_fallback, transport_override, permit_transport_override or a transports list that includes stdio); the same settings in deploy/docsgpt.config.json are not reported. A config file over 1 MB, a manifest over 2 MB, or a lockfile over 32 MiB, is not read.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-DOCSGPT-MCP-STDIO-MITM-001.md: the page then shows that text, with the registry reference appended under it.