Back to CVE records
High 8.9Published Dec 31, 2025

CVE-2025-69286RAGFlow has Predictable Token Generation Leading to Authentication Bypass Vulnerability

Updated under an hour ago ()

Does this affect you?

It affects infiniflow ragflow. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
8.9 HIGH (v4.0, CNA)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:P
Weakness (CWE)
CWE-340
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Jan 2, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
infiniflow ragflow
infiniflow:ragflow (from the name)
before 0.22.0
CNA record
infiniflow ragflow
infiniflow:ragflow
before 0.22.0
NVD

References

  • x-refsource-confirm, exploit, vendor-advisory
  • x-refsource-misc, patch
  • x-refsource-misc, product
  • x-refsource-misc, product
  • x-refsource-misc, product

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.