CVE-2026-26015
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 · uneditedDocsGPT is a GPT-powered chat for documentation. From version 0.15.0 to before version 0.16.0, an attacker accessing both the official DocsGPT website or any local and public deployment, can craft a malicious payload bypassing the "MCP test" behavior to achieve arbitrary remote code execution (RCE). This issue has been patched in version 0.16.0.
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 confidenceDocsGPT versions 0.15.0 through versions prior to 0.16.0 contain a critical vulnerability allowing remote code execution through a malicious payload that bypasses the MCP test functionality. An attacker can achieve arbitrary RCE on any deployment of the affected versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.15.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed DocsGPT versionCheck the version of DocsGPT currently deployed in your environment. This is typically visible in the application UI, startup logs, or by querying the running container/service for its version metadata.Affected if The installed version is 0.15.0 or any version from 0.15.0 up to but not including 0.16.0.
-
Confirm MCP test functionality is enabledLocate the MCP (Model Context Protocol) test feature in the DocsGPT configuration or API. This is typically found in the admin panel, settings file, or feature flags under the MCP or integrations section.Affected if The MCP test functionality is present and enabled in the deployment.
-
Verify MCP test endpoint accessibilityCheck if the MCP test endpoint or interface is exposed to the network. This can be done by reviewing your reverse proxy configuration, firewall rules, and the application's routing configuration to determine if the MCP test route is publicly accessible.Affected if The MCP test functionality is accessible from the network without authentication or from untrusted users.
Your environment is affected if DocsGPT is version 0.15.0 or any version >= 0.15.0 and < 0.16.0, and the MCP test functionality is enabled and accessible to potential attackers.
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.
dbcve · scopedUpgrade DocsGPT to version 0.16.0 or later to apply the security patch that prevents the MCP test bypass leading to RCE.
0.16.0
- Backup your current DocsGPT installation and any persistent data
- Stop the running DocsGPT service
- Download DocsGPT version 0.16.0 from the official repository
- Replace the existing DocsGPT files with version 0.16.0 files
- Restart the DocsGPT service
- Verify the application is running correctly and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26015 — 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-26015 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