CVE-2026-75898
Received Received - Intake

Server-Side Request Forgery in RAGFlow Agent Workflow

Publication date: 2026-08-18

Last updated on: 2026-08-18

Assigner: VulnCheck

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-18
Last Modified
2026-08-18
Generated
2026-08-18
AI Q&A
2026-08-18
EPSS Evaluated
N/A
NVD
CVE-2026-75898
EUVD
EUVD-2026-60824

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
infiniflow ragflow to 0.26.3 (exc)
ragflow ragflow to 0.26.3 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-75898 is a Server-Side Request Forgery (SSRF) vulnerability in RAGFlow's agent workflow 'Invoke' component. The component builds outbound request URLs from user-controlled inputs and sends them via requests.get, requests.post, or requests.put without validating the URL safety. This allows attackers with agent creation or triggering permissions to force the server to access internal network services, loopback addresses, or cloud metadata endpoints, returning responses as component output.

Detection Guidance

To detect this SSRF vulnerability in RAGFlow, check if the Invoke component in agent/component/invoke.py is making outbound requests without SSRF protections. Look for requests to loopback, RFC1918, or metadata service IPs. Use network logs to identify unauthorized outbound connections from the RAGFlow server.

Impact Analysis

An attacker could exploit this to access internal services like cloud metadata endpoints to steal credentials, interact with co-located services on the deployment network, or perform unauthorized actions via crafted requests. If chat queries are interpolated into the Invoke URL, anyone sending queries could control the target destination.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive internal data, potentially violating confidentiality requirements in GDPR and HIPAA. Unauthorized data exfiltration or modification via SSRF may result in compliance breaches, data protection violations, and regulatory penalties.

Mitigation Strategies

Upgrade RAGFlow to version 0.26.3 or later to apply the SSRF fix. Ensure the Invoke component now calls assert_url_is_safe and pin_dns before making requests. Block requests to internal IPs and disable redirect following in HTTP calls.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-75898. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart