CVE-2026-121927
InfiniFlow RAGFlow Seafile Connector seafile_connector.py _account_get server-side request forgery
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| RAGFlow InfiniFlow |
0.27.0 (affected) 0.27.1 (affected) 0.27.2 (affected) 0.27.3 (affected) |
CNA: VulDB |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 5.3 medium |
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/E:P | CNA: VulDB |
| 3.1 / 6.3 medium |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C | CNA: VulDB |
| 3.0 / 6.3 medium |
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C | CNA: VulDB |
| 2.0 / 6.5 medium |
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:C | CNA: VulDB |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://vuldb.com/vuln/431037CNA: VulDB · vdb-entry, technical-description
- https://vuldb.com/vuln/431037/ctiCNA: VulDB · signature, permissions-required
- https://vuldb.com/cve/CVE-2026-121927CNA: VulDB · third-party-advisory
- https://vuldb.com/submit/1023351CNA: VulDB · third-party-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.