Skip to main content

Ragflow EUVDEUVD-2026-18876

| CVE-2026-28797 HIGH
Improper Input Validation (CWE-20)
2026-04-03 GitHub_M
8.7
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to RAGFlow application
  2. Exploit
    Create Agent workflow with StringTransform component
  3. Execution
    Inject malicious Jinja2 template syntax
  4. Impact
    Execute arbitrary OS commands via unsandboxed template rendering

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Requires authenticated user access to RAGFlow 0.24.0 or prior. Attacker must have login credentials to exploit SSTI vulnerability in Agent workflow StringTransform or Message components. Remote network access required; no victim interaction needed.

Impact

This vulnerability presents high real-world risk for organizations running RAGFlow in multi-user or internet-exposed environments. The CVSS 4.0 vector (AV:N/AC:L/PR:L) indicates network-accessible exploitation with low complexity requiring only low-privilege authentication, resulting in complete confidentiality, integrity, and availability impact (VC:H/VI:H/VA:H). EPSS data not provided, but the combination of remote attack vector, low complexity, and RCE capability typically correlates with elevated exploitation probability once details are public. No CISA KEV listing indicates no confirmed active exploitation in federal enterprise networks. The authentication requirement (PR:L) provides minimal barrier since RAGFlow is designed for multi-user access, and any legitimate account holder becomes a potential threat vector. The absence of vendor patch at publication time significantly elevates risk, forcing organizations to choose between continued exposure or disabling affected functionality. This represents a critical priority for any deployment with untrusted authenticated users, though risk is somewhat mitigated in single-user or fully trusted environments. The vulnerability is likely automatable once credentials are obtained, making it suitable for post-compromise lateral movement scenarios.

Exploit ScenarioDerived

An authenticated attacker with a low-privilege account on a RAGFlow instance creates a new Agent workflow and adds a Text Processing or Message component. Within the component's template field, the attacker injects a malicious Jinja2 template such as {{config.__class__.__init__.__globals__['os'].popen('whoami').read()}} or similar Python object traversal payload. When the workflow executes, the unsandboxed Jinja2 renderer processes the template, executing the embedded OS command and returning output to the attacker. The attacker can escalate to persistent backdoors, data exfiltration, or pivot to other network resources using the compromised RAGFlow server's privileges. No public exploit identified at time of analysis, but the technical details in the advisory provide sufficient information for skilled attackers to develop working exploits.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 03, 2026

Server-Side Template Injection in RAGFlow 0.24.0 and earlier allows authenticated users to execute arbitrary OS commands via unsandboxed Jinja2 template rendering in Agent workflow components. The vulnerability affects the Text Processing (StringTransform) and Message components, where user-supplied templates are processed without sandboxing. With a CVSS 8.7 score and low attack complexity (AC:L), authenticated attackers can achieve full system compromise remotely. No public exploit identified at time of analysis, and no vendor-released patch available as of publication date.

RemediationAI

No vendor-released patch identified at time of analysis according to the published advisory. Organizations should immediately review access controls and restrict RAGFlow usage to fully trusted users only until a fix becomes available. Monitor the official GitHub Security Advisory at https://github.com/infiniflow/ragflow/security/advisories/GHSA-vvwj-fvwh-4whx for patch announcements and subscribe to the infiniflow/ragflow repository release notifications. As an interim mitigation, consider disabling or restricting access to the Agent workflow's Text Processing (StringTransform) and Message components if business requirements permit. Implement network segmentation to isolate RAGFlow servers from critical infrastructure and sensitive data stores. Enhanced monitoring for unusual process execution, outbound network connections, or file system modifications from RAGFlow server processes can provide early detection of exploitation attempts. If the application architecture permits, consider running RAGFlow in containerized environments with restricted capabilities and read-only file systems to limit post-exploitation impact. Review authentication logs for suspicious account activity and enforce strong authentication mechanisms to raise the barrier for initial access.

Affected VersionsENISA

ragflow ≤ 0.24.0

Affected Packages

euvd ragflow no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

RAGFlow is an open-source Retrieval-Augmented Generation engine (cpe:2.3:a:infiniflow:ragflow) that processes user queries using AI-powered document retrieval workflows. The vulnerability stems from unsafe use of Python's jinja2.Template class in the Agent workflow's StringTransform and Message components. Jinja2 is a powerful templating engine commonly used in Python web applications, but when used without sandboxing (specifically, without jinja2.sandbox.SandboxedEnvironment), it allows template authors to access Python internals and execute arbitrary code. The root cause is classified as CWE-20 (Improper Input Validation), though this more specifically represents a template injection vulnerability where user-controlled template content is rendered without sanitization. Authenticated users can craft malicious Jinja2 templates containing Python code that executes in the server context, bypassing application-level security controls entirely.

Know when Ragflow gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine. In versions 0.24.0 and prior, a Server-Side Template Injection (SSTI) vulnerability exists in RAGFlow's Agent workflow Text Processing (StringTransform) and Message components. These components use Python's jinja2.Template (unsandboxed) to render user-supplied templates, allowing any authenticated user to execute arbitrary operating system commands on the server. At time of publication, there are no publicly available patches.

Executive ViewAI

Why It Matters

RAGFlow versions 0.24.0 and earlier contain a server-side template injection flaw that allows authenticated internal users to execute arbitrary operating system commands and compromise affected systems. Organizations using RAGFlow for AI workflow automation face elevated risk of data exfiltration and system takeover by privileged users or compromised accounts with agent access.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict agent workflow component access via RBAC to minimal set of trusted administrators; (2) Implement network segmentation to limit RAGFlow server lateral movement; (3) Enable audit logging for all agent workflow modifications and monitor for template injection patterns (e.g., Jinja2 syntax like {{ }}, {% %}); (4) Disable Agent workflow features entirely if not operationally critical; (5) Evaluate sandboxed template rendering alternatives in vendor roadmap.

Threat Intelligence Overview

EPSS Score
0.1%
Top 74% exploitable
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

CVE-2024-12433 CRITICAL POC
9.8 Mar 20

A vulnerability in infiniflow/ragflow versions v0.12.0 allows for remote code execution. Rated critical severity (CVSS 9

CVE-2026-24770 CRITICAL POC
9.8 Jan 27

Path traversal vulnerability in RAGFlow RAG engine version 0.23.1 allows unauthenticated attackers to read arbitrary fil

CVE-2024-12450 CRITICAL POC
9.8 Mar 20

In infiniflow/ragflow versions 0.12.0, the `web_crawl` function in `document_app.py` contains multiple vulnerabilities.

CVE-2025-27135 HIGH POC
8.9 Feb 25

RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine. Rated high severity (CVSS 8.9), this vulnerabilit

CVE-2025-69286 HIGH POC
8.9 Dec 31

RAGFlow versions prior to 0.22.0 generate API keys and beta assistant/agent share tokens with a predictable scheme, lett

CVE-2024-10131 HIGH POC
8.8 Oct 19

The `add_llm` function in `llm_app.py` in infiniflow/ragflow version 0.11.0 contains a remote code execution (RCE) vulne

CVE-2025-68700 HIGH POC
8.6 Dec 31

Remote code execution in RAGFlow versions prior to 0.23.0 allows a low-privileged authenticated user (a normal login acc

CVE-2025-25282 HIGH POC
8.1 Feb 21

RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine based on deep document understanding. Rated high s

CVE-2024-12779 HIGH POC
7.5 Mar 20

A Server-Side Request Forgery (SSRF) vulnerability exists in infiniflow/ragflow version 0.12.0. Rated high severity (CVS

CVE-2024-53450 HIGH POC
7.5 Dec 09

RAGFlow 0.13.0 suffers from improper access control in document-hooks.ts, allowing unauthorized access to user documents

CVE-2024-12880 MEDIUM POC
6.5 Mar 20

A vulnerability in infiniflow/ragflow version RAGFlow-0.13.0 allows for partial account takeover via insecure data query

CVE-2026-45312 CRITICAL
9.9 May 29

Server-side template injection in RAGFlow 0.24.0 and earlier allows any authenticated user to execute arbitrary operatin

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy