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.
CVE-2026-58579
Score 5.4 from GitHub Security Advisory published 2026-07-02. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EPSS
- 7.9%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 6, 2026
References (5)
- disclosure@vulncheckhttps://github.com/infiniflow/ragflow/commit/572f1ea9f4eba6a60e64f7437dee60aa1c0913f1
- disclosure@vulncheckhttps://github.com/infiniflow/ragflow/issues/16507
- disclosure@vulncheckhttps://github.com/infiniflow/ragflow/pull/16516
- disclosure@vulncheckhttps://github.com/infiniflow/ragflow/releases/tag/v0.26.3
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/ragflow-stored-cross-site-scripting-via-agent-pipeline-node-name
Vendor Advisories for CVE-2026-58579(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 17:12 UTCEG score recompute
- 2026-07-06 17:12 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 14:21 UTCMITRE cvelistV5CVSS v4 → 5.1
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 18:26 UTCEG score recompute
- 2026-07-05 18:25 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 19:39 UTCEG score recompute
- 2026-07-04 19:39 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 20:53 UTCEG score recompute
- 2026-07-03 20:53 UTCGHSA enrichment
- 2026-07-02 22:07 UTCEG score recompute
- 2026-07-02 22:07 UTCGHSA enrichment
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58579?
When was CVE-2026-58579 disclosed?
Is CVE-2026-58579 actively exploited?
What is the CVSS score of CVE-2026-58579?
How do I remediate CVE-2026-58579?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58579
Is Your Infrastructure Affected by CVE-2026-58579?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.