dbcve.org
RagflowApplication · Infiniflow

CVE-2025-69286

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-31
Fix available
A fix is available. Upgrade to 0.22.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RAGFlow versions before 0.22.0 use a weak key generation mechanism where both API keys and beta (assistant/agent share auth) tokens are generated using the same URLSafeTimedSerializer with predictable inputs. An attacker who obtains a shared assistant/agent URL can reverse-engineer the token to derive the owner's personal API key, achieving full account takeover.

MitigationUpgrade to RAGFlow version 0.22.0 or later, which implements a cryptographically separate key generation algorithm for API keys versus beta tokens.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RagflowApplication
Affected:< 0.22.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RAGFlow version
    Check the RAGFlow version running in your environment (typically via docker images, package metadata, or the /api/v1/version endpoint if exposed)
    Affected if The installed version is before 0.22.0
  2. Locate API key generation code
    Inspect the source code or running application to find where API keys are generated, looking for uses of URLSafeTimedSerializer or similar token generation methods
    Affected if The API key generation uses URLSafeTimedSerializer with predictable inputs
  3. Locate beta token generation code
    Inspect the source code or running application to find where beta (assistant/agent share auth) tokens are generated, looking for uses of URLSafeTimedSerializer or similar token generation methods
    Affected if The beta token generation uses URLSafeTimedSerializer with predictable inputs
  4. Compare generation mechanisms
    Determine whether both API keys and beta tokens are generated using the same URLSafeTimedSerializer instance with the same secret/salt inputs
    Affected if Both API keys and beta tokens are generated using the same URLSafeTimedSerializer with identical predictable inputs

You are affected if your RAGFlow version is before 0.22.0 and both API keys and beta tokens are generated using the same URLSafeTimedSerializer with predictable inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.22.0 or later
Fixed in 0.22.0
Vendor patch github.com →
Interim mitigation

Upgrade to RAGFlow version 0.22.0 or later, which implements a cryptographically separate key generation algorithm for API keys versus beta tokens.

Recommended fix High confidence

0.22.0

  1. Back up your existing Ragflow data and configuration files before upgrading
  2. Stop the Ragflow service
  3. Upgrade Ragflow to version 0.22.0 (for Docker: 'docker pull infiniflow/ragflow:v0.22.0', then recreate the container; for other installations, update to the v0.22.0 release
  4. Restart the Ragflow service
  5. After upgrading, regenerate any existing API keys and beta tokens to ensure they use the new secure key generation algorithm

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ragflow Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69286 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data