CVE-2025-69286: infiniflow ragflow · Generation of Predictable Numbers or Identifiers
Affects infiniflow ragflowSource CVE Database V5
Public exploit available · CVSS 8.9 High : upgrade to 0.22.0 as a priority.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.22.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 31 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade infiniflow/ragflow to 0.22.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubinfiniflow/ragflowpkg:github/infiniflow/ragflowOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade all RAGFlow deployments to version 0.22.0 or later immediately to apply the fixed key generation mechanism.
- Audit all shared assistant/agent URLs and beta tokens in use; revoke and regenerate tokens where possible to invalidate potentially compromised keys.
- Implement strict access controls around token sharing, limiting distribution to trusted personnel and systems only.
- Monitor logs for unusual access patterns or token usage indicative of unauthorized derivation attempts.
- Employ network segmentation and least privilege principles to limit the impact of any compromised account.
- Consider additional layers of authentication or token validation mechanisms external to RAGFlow to detect anomalies.
- Educate developers and administrators on secure token generation and handling practices to prevent recurrence.
- Regularly review and update cryptographic libraries and dependencies to ensure use of secure random number generators and serializers.
Description
RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine. In versions prior to 0.22.0, the use of an insecure key generation algorithm in the API key and beta (assistant/agent share auth) token generation process allows these tokens to be mutually derivable. Specifically, both tokens are generated using the same `URLSafeTimedSerializer` with predictable inputs, enabling an unauthorized user who obtains the shared assistant/agent URL to derive the personal API key. This grants them full control over the assistant/agent owner's account. Version 0.22.0 fixes the issue.
References
- github.com/infiniflow/ragflow/security/advisories/GHSA-9j5g-g4xm-57w7 (opens in a new tab)
- github.com/infiniflow/ragflow/commit/a3bb4aadcc3494fb27f2a9933b4c46df8eb532e6 (opens in a new tab)
- github.com/infiniflow/ragflow/blob/v0.20.5/api/apps/system_app.py (opens in a new tab)
- github.com/infiniflow/ragflow/blob/v0.20.5/api/utils/__init__.py (opens in a new tab)
- github.com/infiniflow/ragflow/blob/v0.20.5/api/utils/api_utils.py (opens in a new tab)