# CVE-2026-121928: InfiniFlow RAGFlow Images API file_utils.py cross site scripting


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-8jq6-8g6v-g3cr

## What is CVE-2026-121928?

CVE-2026-121928 is a medium-severity vulnerability in InfiniFlow RAGFlow, published on 4 Nov 2026. 

### Official description

A vulnerability was identified in InfiniFlow RAGFlow up to 0.27.2. This issue affects some unknown processing of the file api/utils/file_utils.py of the component Images API. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. Upgrading to version 0.27.3 is capable of addressing this issue. The identifier of the patch is 9ea0246f8d453a144fb4f903d163b2ba6b91ed2c. Upgrading the affected component is advised.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

No fix has been published for CVE-2026-121928 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121928 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121928 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121928 and fix it if it is affected.

What it is: CVE-2026-121928 is a medium-severity vulnerability in InfiniFlow RAGFlow, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121928 exists.

Affected product: InfiniFlow RAGFlow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121928/ (Markdown: https://insights.sbomify.com/CVE-2026-121928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121928
- OSV: https://osv.dev/vulnerability/CVE-2026-121928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121928/
Summaries are generated and may contain mistakes; the official description above is the record.