CVE Intelligence
Analysis AI-assisted

CVE-2026-26015: DocsGPT Unauthenticated RCE via MCP STDIO Configuration

DocsGPT versions from 0.15.0 up to before 0.16.0 are affected by a critical command injection flaw (CWE-77) that, according to the record, can lead to arbitrary remote code execution. The issue is reported as patched in version 0.16.0, and the record shows no confirmed exploitation in the sources consulted.

Published Oct 24, 2026 · Updated Oct 24, 2026 · Ler em português

Overview

DocsGPT is a GPT-powered chat for documentation. This advisory describes a command injection weakness (CWE-77) in the MCP STDIO configuration handling. According to the record, it can be used to achieve arbitrary remote code execution, and the issue was patched in version 0.16.0.

Impact

  • The description states that successful exploitation leads to arbitrary remote code execution, which would give an attacker control over the affected host process.
  • NVD assigns a CVSS base score of 9.8 (critical). The GitHub CNA record lists a score of 10.
  • The SSVC data in the record rates technical impact as total and automatable as yes.

Affected products and versions

  • Product: Arc53 DocsGPT.
  • Versions from 0.15.0 up to before 0.16.0 are listed as affected.
  • Version 0.16.0 is the version in which the issue was patched.

Exploitation status

  • CISA KEV does not list this CVE in the record, so no confirmed active exploitation is recorded there.
  • No confirmed exploitation appears in the sources consulted.
  • The SSVC exploitation value in the record is 'poc', which indicates that proof-of-concept material is recognized. One GitHub advisory reference is tagged as exploit-related.

Remediation and mitigation

  • Upgrade DocsGPT to version 0.16.0 or later, as stated in the description and the linked release notes.
  • Inventory every DocsGPT deployment, including local, internal and public instances, and confirm the running version.
  • Until the upgrade is complete, limit network exposure of DocsGPT instances and restrict access to MCP configuration and test features.
  • Review MCP server entries for unexpected changes after the upgrade.

Detection guidance

  • Review web and application logs for unusual requests to MCP configuration or test functionality.
  • Watch for unexpected child processes started by the DocsGPT service.
  • Audit MCP STDIO configuration for entries that were not created by administrators.

Limitations of the available information

  • The record's fixes list is empty. The patched version is taken from the description and the 0.16.0 release link, not from structured fix data.
  • The record does not detail the exact trigger conditions or the authentication boundary, although the description says no authentication is required.
  • The EPSS date in the record (2026-10-23) is later than the publication date (2026-04-29), so the timing of that score should be verified.

Frequently asked questions

Which DocsGPT versions are affected?

According to the record, versions from 0.15.0 up to before 0.16.0 are affected by this issue.

Is there a fix?

The description states that the issue was patched in version 0.16.0. The record's structured fixes list is empty, so confirm the fix against the linked release notes.

Is this vulnerability known to be exploited in the wild?

No. The record shows this CVE is not listed in CISA KEV, and no confirmed exploitation appears in the sources consulted.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.