Loading vulnerability…
CVE-2026-26015 is a command injection / remote code execution vulnerability in DocsGPT affecting version 0.15.0 through versions before 0.16.0. According to the provided context, an attacker can craft a malicious payload that bypasses the application's "MCP test" behavior. The issue is tied to unsafe handling of MCP configuration and transport processing, including mention of changing configured JSON transport to STDIO instead of SSE or HTTP, resulting in execution of attacker-controlled commands on the host. The vulnerability affects both the official DocsGPT website and self-hosted local or publicly exposed deployments.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability in DocsGPT affecting versions 0.15.0 through before 0.16.0, where a malicious payload can bypass the "MCP test" behavior and achieve arbitrary code execution.
A vulnerability in DocsGPT related to unsafe MCP STDIO configuration that can lead to command execution; the article states it is patched.
A critical command injection vulnerability in DocsGPT where crafted network requests can switch MCP transport to STDIO and inject arbitrary commands for remote code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.