Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-31020 – Unauthenticated RCE via Server-Side Template Injection – DocsGPT ≤ 0.15.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-31020 is a critical Server-Side Template Injection (SSTI) vulnerability in DocsGPT, an open-source AI-powered document chat/agent platform. The custom prompt feature renders user-supplied prompt content using Jinja templates without sanitization or sandboxing, allowing an unauthenticated attacker to inject malicious Jinja expressions and achieve full remote code execution on the server. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: DocsGPT’s custom prompt functionality passes user-supplied prompt text directly into a Jinja template rendering engine without input sanitization or use of a sandboxed template environment.
  • Trigger conditions: An attacker submits a crafted custom prompt containing Jinja template syntax/expressions (e.g., accessing Python object internals) through the exposed prompt configuration feature.
  • Attack vector: Network-based, requires no authentication and no user interaction (AV:N, PR:N, UI:N).
  • Impact: Successful exploitation allows arbitrary code execution on the underlying server, giving the attacker full compromise of confidentiality, integrity, and availability of the application and host — including potential access to stored documents, API keys/credentials, and connected backend systems.
  • Classification: CWE-94 (Improper Control of Generation of Code / Code Injection).

Affected software

  • DocsGPT versions 0.15.0 and earlier (custom prompt / Jinja templating feature).

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade DocsGPT to the latest available release, and verify that the version in use no longer renders user-supplied custom prompt content through an unsandboxed Jinja Environment. At the time of writing, no vendor security advisory or dedicated patched version number has been publicly confirmed for this specific CVE — organizations should track the official DocsGPT repository and release notes for a fix addressing this issue and apply it as soon as it is available.
  • If no patch is available:
    • Disable or restrict access to the custom prompt configuration feature until a fix is confirmed and applied.
    • Do not expose DocsGPT instances (especially the prompt/admin configuration endpoints) directly to the public internet; restrict access via VPN, IP allow-listing, or authentication at a reverse proxy/gateway layer.
    • Deploy the application with least-privilege service account permissions and run it in an isolated/sandboxed environment (e.g., container with restricted filesystem/network access) to limit the impact of code execution if exploited.
    • Monitor logs for anomalous prompt content containing template syntax (e.g., {{, {%, references to Python builtins/class internals) as an indicator of exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge