CVE-2026-58579: infiniflow ragflow · Cross-site Scripting
Affects infiniflow ragflowSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 0.26.3 when convenient.
Data as of 14 Nov 2026, 20:58 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 3.1 | 5.4 |
|---|---|---|
| CNA (VulnCheck) | CVSS 4.0 | 5.1 |
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.26.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade infiniflow ragflow to 0.26.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| infiniflowragflow | Affected
| Fixed in
|
GitHubragflowpkg:github/ragflowOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to RAGFlow version 0.26.3 or later once available, as this version presumably addresses the issue. Until then, restrict agent creation and editing permissions to trusted users only to reduce risk. Monitor vendor advisories for an official patch or remediation guidance.
Description
RAGFlow before 0.26.3 stores an agent pipeline (DSL) node name without sanitization: the agent update endpoint normalizes the submitted DSL via normalize_dsl, which only performs JSON serialization validation and preserves the node name verbatim. The dataflow-result web UI then renders that name into the "Rerun from current step" confirmation modal via dangerouslySetInnerHTML, and the i18next configuration sets escapeValue:false, so the value is inserted into the DOM without HTML encoding. An authenticated workspace user who can create or edit an agent can inject arbitrary JavaScript that executes in the session of another workspace member who opens the dataflow result and clicks rerun, enabling session/token theft and account takeover across the user trust boundary.
References
- github.com/infiniflow/ragflow/releases/tag/v0.26.3 (opens in a new tab)
- github.com/infiniflow/ragflow/issues/16507 (opens in a new tab)
- github.com/infiniflow/ragflow/pull/16516 (opens in a new tab)
- github.com/infiniflow/ragflow/commit/572f1ea9f4eba6a60e64f7437dee60aa1c0913f1 (opens in a new tab)
- vulncheck.com/advisories/ragflow-stored-cross-site-scripting-via-agent-pipeline-node-name (opens in a new tab)