RAGFlow < 0.26.3 - Server-Side Request Forgery via Agent Invoke Component
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| infiniflow | ragflow | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Infiniflow | Ragflow |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.393% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | RAGFlow < 0.26.3 - Server-Side Request Forgery via Agent Invoke Component | |
| First Time appeared |
Infiniflow
Infiniflow ragflow |
|
| Weaknesses | CWE-918 | |
| CPEs | cpe:2.3:a:infiniflow:ragflow:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Infiniflow
Infiniflow ragflow |
|
| References |
|
|
| Metrics |
cvssV3_1
|