---
id: "CVE-2026-121927"
kind: "vulnerability"
aliases: ["CVE-2026-121927"]
title: "RAGFlow: Seafile connector lets attackers make the server send requests"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "ragflow", "fixed": [], "affected": ">= 0.27.0, <= 0.27.3", "ecosystem": "vendor"}]
ecosystems: []
tags: ["ai-rag", "ai-tooling", "ragflow", "seafile", "self-hosted"]
not_affected_if: ["newer-version", "no-seafile-connector"]
published_at: "2026-11-04T18:17:42+00:00"
first_seen_at: "2026-11-04T18:28:34+00:00"
updated_at: "2026-11-04T18:31:14+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-121927", "first_seen_at": "2026-11-04T18:28:34+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-04T18:31:14+00:00"}]
---

# RAGFlow: Seafile connector lets attackers make the server send requests

RAGFlow, an open-source retrieval-augmented generation platform, has a server-side request forgery flaw in its Seafile connector. An attacker who controls the seafile_url setting can make the server send requests to internal or external addresses of their choosing.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:ragflow affected >= 0.27.0, <= 0.27.3 fixed ?

## How to check

- Find your RAGFlow version (image tag or release file); 0.27.0 through 0.27.3 are listed as affected.
- Check whether any dataset uses a Seafile data source, and who can add or edit data sources.
- Also check whether a RAGFlow release newer than 0.27.3 is out and whether its seafile_connector.py validates seafile_url (for example with the common/ssrf_guard helper); I could not confirm this.

## Timeline

- 2026-11-04T18:28:34+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-121927
- 2026-11-04T18:31:14+00:00 analyst — VulDB (CNA) says the vendor did not respond; no vendor advisory, no fixed version found in the RAGFlow advisories or releases I read. A public PoC is claimed by VulDB (submit #1023351, tested at v0.27.1), but I found no link to it. Nothing verified: no primary vendor page. The login requirement is inferred from PR #12945, not stated by the CVE. NVD gives CVSS v4 PR:L, which suggests low privileges are needed.

## Documents

- [describes] VulDB VDB-431037: RAGFlow Seafile connector SSRF https://vuldb.com/vuln/431037
- [mentions] feat(connector): add Seafile as data source (PR #12945) https://github.com/infiniflow/ragflow/pull/12945

## From the sources

A vulnerability has been found in InfiniFlow RAGFlow up to 0.27.3. Affected by this issue is the function _account_get of the file common/data_source/seafile_connector.py of the component Seafile Connector. Such manipulation of the argument seafile_url leads to server-side request forgery. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_