RAGFlow before 0.26.3 contains a server-side request forgery vulnerability in the agent workflow "Invoke" component (agent/component/invoke.py). The component builds an outbound request URL from canvas configuration and runtime template variables and passes it to requests.get, requests.post, or requests.put without calling the shared assert_url_is_safe validator or pinning the resolved address, unlike the crawler, SearXNG, file-upload, and RSS fetch paths. A user who can create or trigger an agent can direct the server to fetch loopback, link-local, and RFC 1918 destinations, including cloud instance metadata endpoints and services co-located on the deployment network, and the response body is returned as the component output. Where an agent is configured to interpolate the chat query into the Invoke URL, the destination is chosen by whoever can send that query.
CVE-2026-75898
Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-18. a secondary CVSS source baseline 8.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(high)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity85% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (7)
Auto-updated Aug 18, 2026RAGFlow < 0.26.3 - Server-Side Request Forgery via Agent Invoke Component | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ragflow-server-side-request-forgery-via-agent-invoke-componentcommit c4fe68eaa0bf (infiniflow/ragflow)
Fix landed in infiniflow/ragflow commit c4fe68eaa0bf — awaiting tagged release
https://github.com/infiniflow/ragflow/commit/c4fe68eaa0bf1d6442d2cd6ac2e35bc9ccbed34fcommit e16d1a0150e1 (infiniflow/ragflow)
Fix landed in infiniflow/ragflow commit e16d1a0150e1 — awaiting tagged release
https://github.com/infiniflow/ragflow/commit/e16d1a0150e1ca069beb538ae3dcd03f59edc5faragflow/agent/component/invoke.py at v0.26.2 · infiniflow/ragflow · GitHub
https://github.com/infiniflow/ragflow/blob/v0.26.2/agent/component/invoke.py#L168-L172Server-Side Request Forgery (SSRF) in the agent "Invoke" HTTP component allows any authenticated user to reach internal network services · Issue #18280 · infiniflow/ragflow · GitHub
https://github.com/infiniflow/ragflow/issues/18280[Bug]: Agent Invoke component lacks SSRF guard on outbound requests · Issue #15425 · infiniflow/ragflow · GitHub
https://github.com/infiniflow/ragflow/issues/15425v0.26.3
Patch available: infiniflow/ragflow v0.26.3
https://github.com/infiniflow/ragflow/releases/tag/v0.26.3Vendor Advisories for CVE-2026-75898(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 14× in last 7d / 14× 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-08-21 04:02 UTCEG score recompute
- 2026-08-21 04:02 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:54 UTCGHSA enrichment
- 2026-08-20 03:45 UTCEG score recompute
- 2026-08-20 03:45 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:36 UTCGHSA enrichment
- 2026-08-19 03:28 UTCEG score recompute
- 2026-08-19 03:28 UTCGHSA enrichment
- 2026-08-18 15:19 UTCEG score recompute
- 2026-08-18 14:50 UTCEG score recompute
- 2026-08-18 14:32 UTCEG score recompute
- 2026-08-18 14:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-75898?
When was CVE-2026-75898 disclosed?
Is CVE-2026-75898 actively exploited?
What is the CVSS score of CVE-2026-75898?
How do I remediate CVE-2026-75898?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75898
Is Your Infrastructure Affected by CVE-2026-75898?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.