Quick answers
- Is CVE-2025-68700 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-68700 being exploited in the wild.
- How severe is CVE-2025-68700?
- High severity, with a CVSS score of 8.8, published 31 December 2025.
- Which products and versions are affected?
- InfiniFlow RAGFlow prior to 0.23.0.
- Is there a fix for CVE-2025-68700?
- A patch was published on 2025-11-25: Version 0.23.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-68700 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-68700?
- Check whether you run InfiniFlow RAGFlow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in agent/tools/code_exec.py where untrusted stdout output from a sandboxed execution environment is directly passed to Python's eval() function with no filtering or validation. An authenticated attacker can craft a CodeExec node that prints a Python expression designed to execute arbitrary code; when eval() processes this expression, it executes on the host process with full privileges. The root cause is the use of eval() for automatic type conversion without proper input sanitization. The attack requires prior authentication and network access to the RAGFlow frontend, but no additional user interaction beyond node execution. The patch in version 0.23.0 replaces unsafe eval() usage with safe deserialization methods like json.loads().
Affected products
- Infiniflow RAGFlow prior to 0.23.0
Timeline
- 2025-12-31: disclosed
- 2025-11-25: patched: Version 0.23.0 released with fix
- 2025-11-25: other: Fix commit 7a344a32f9f83529e12ca12f40f2657eb79fe811 merged to main