# CVE-2026-45312: RAGFlow: Server-Side Template Injection in Prompt Generator leads to Remote Code Execution

> Authenticated users can execute arbitrary OS commands via Jinja2 template injection in the prompt generator, requiring an upgrade to secure the RAGFlow engine.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-wpg4-h5g2-jxm6

## What is CVE-2026-45312?

CVE-2026-45312 is a critical code injection vulnerability in infiniflow ragflow, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine. In 0.24.0 and earlier, a Jinja2 template injection in the prompt generator (rag/prompts/generator.py) allows any authenticated user to execute arbitrary OS commands on the server. Any normal user can register, create a Canvas workflow with a DuckDuckGo + LLM component chain, and trigger the SSTI.

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

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


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

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

## Is CVE-2026-45312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45312 is a critical code injection vulnerability in infiniflow ragflow, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45312 exists.

Affected product: infiniflow ragflow. 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-45312/ (Markdown: https://insights.sbomify.com/CVE-2026-45312/index.md)
```

## Sources

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

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