Security readout for executives and security teams
Plain-English summary
RAGFlow versions 0.24.0 and earlier have a critical flaw that can let a logged-in user run operating-system commands on the server. If registration or normal user access is broadly available, the business risk is severe: server takeover, data theft, service disruption, and pivoting are plausible outcomes.
Executive priority
Emergency priority for any exposed or multi-user RAGFlow deployment. The risk is not theoretical from a design standpoint: the reported impact is remote code execution by authenticated normal users. Contain access now, verify versions, and follow vendor remediation guidance before continued broad use.
Technical view
The issue is a Jinja2 server-side template injection in RAGFlow's prompt generator, identified in rag/prompts/generator.py. The source says any authenticated user can reach the vulnerable behavior through a Canvas workflow path involving DuckDuckGo and LLM components. CVSS 9.9 reflects low attack complexity, low privileges, no user interaction, changed scope, and full CIA impact.
Likely exposure
Organizations running infiniflow RAGFlow 0.24.0 or earlier are potentially exposed, especially if the service is internet-accessible, allows self-registration, or permits untrusted authenticated users. Evidence in the bundle identifies only RAGFlow as affected; no other products are supported by the provided sources.
Exploitation context
The CVE source describes a low-privilege authenticated path to arbitrary OS command execution. The bundle marks KEV as false, and no cited source states active exploitation. Treat exposure as urgent because normal user access may be enough, but do not assume exploitation has occurred without environment evidence.
Researcher notes
The provided evidence supports CWE-1336, affected versions through 0.24.0, and authenticated RCE via Jinja2 SSTI in the prompt generator. The bundle does not provide a fixed version, detailed patch, or active exploitation confirmation. Validate through inventory and configuration review rather than reproducing the exploit path.
Mitigation direction
- Review the GitHub advisory for the vendor-named fixed release or mitigation.
- Restrict RAGFlow access to trusted users and trusted networks immediately.
- Disable open self-registration where it is enabled.
- Limit or suspend untrusted Canvas workflow creation until remediation is confirmed.
- Prioritize upgrading affected RAGFlow instances when vendor guidance identifies a safe version.
Validation and detection
- Inventory all RAGFlow deployments and record their exact versions.
- Flag any RAGFlow instance running 0.24.0 or earlier.
- Confirm whether self-registration or broad authenticated access is enabled.
- Identify internet-exposed or partner-accessible RAGFlow services.
- Review logs for unusual workflow creation or low-privilege server-side activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1336: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45312 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/infiniflow/ragflow/security/advisories/GHSA-wpg4-h5g2-jxm6CVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements Used in a Template Engine
Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.