# CVE-2026-123020: eosphoros-ai DB-GPT Jinja2 Template __init__.py FileBasedSkill.get_prompt special elements in template engine


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-x327-5gx8-j9v4

## What is CVE-2026-123020?

CVE-2026-123020 is a medium-severity vulnerability in eosphoros-ai DB-GPT, published on 5 Nov 2026. 

### Official description

A security vulnerability has been detected in eosphoros-ai DB-GPT up to 0.8.1. The affected element is the function FileBasedSkill.get_prompt of the file packages/dbgpt-core/src/dbgpt/agent/skill/claude_skill/__init__.py of the component Jinja2 Template Handler. The manipulation leads to improper neutralization of special elements used in a template engine. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 0.8.2 is sufficient to fix this issue. The identifier of the patch is a9e7a3c026d114fcfb4ffe3eaf78851a636ded16. It is suggested to upgrade the affected component.

Weakness: CWE-791 (Incomplete Filtering of Special Elements), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-123020?


## How do I fix CVE-2026-123020?

No fix has been published for CVE-2026-123020 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123020 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123020 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123020 and fix it if it is affected.

What it is: CVE-2026-123020 is a medium-severity vulnerability in eosphoros-ai DB-GPT, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123020 exists.

Affected product: eosphoros-ai DB-GPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123020/ (Markdown: https://insights.sbomify.com/CVE-2026-123020/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123020
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123020
- OSV: https://osv.dev/vulnerability/CVE-2026-123020

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123020/
Summaries are generated and may contain mistakes; the official description above is the record.