{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69286 exists.","fix":"No fix has been published for CVE-2025-69286 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69286 is a high-severity authentication bypass vulnerability in infiniflow ragflow, published on 31 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-69286 and fix it if it is affected.\n\nWhat it is: CVE-2025-69286 is a high-severity authentication bypass vulnerability in infiniflow ragflow, published on 31 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69286 exists.\n\nAffected product: infiniflow ragflow. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-69286/ (Markdown: https://insights.sbomify.com/CVE-2025-69286/index.md)","id":"CVE-2025-69286","markdown":"https://insights.sbomify.com/CVE-2025-69286/index.md","name":"CVE-2025-69286","record":{"aliases":["GHSA-9j5g-g4xm-57w7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"RAGFlow RAG engine","requires_auth":"none","summary":"Attackers can derive API keys from shared URLs due to predictable token generation, leading to full account takeover in RAGFlow.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ragflow","vendor":"infiniflow"}],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-340","name":"Generation of Predictable Numbers or Identifiers"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-11","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-11T02:36:51Z","kind":"github_poc","ref":"https://github.com/qianlijaingshan/ragflow-audit","stars":1,"title":"RAGFlow 三洞审计工具 (CVE-2026-28797 / CVE-2026-24770 / CVE-2025-69286)"}],"tier":"weaponised"},"has_fix":false,"headline":"RAGFlow has Predictable Token Generation Leading to Authentication Bypass Vulnerability","id":"CVE-2025-69286","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"BSV Blockchain SDK has an Authentication Signature Data Preparation Vulnerability","id":"CVE-2025-69287"},"packages":[],"prev":{"headline":"SQLBot uploadExcel Endpoint has Unauthenticated Arbitrary File Upload vulnerability","id":"CVE-2025-69285"},"products":["ragflow"],"published":"2025-12-31","related":[{"cvss_score":9.8,"headline":"RAGFlow Affected by Zip Slip Remote Code Execution (RCE) in MinerUParser","id":"CVE-2026-24770","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":9.8,"headline":"Remote Code Execution in infiniflow/ragflow","id":"CVE-2024-12433","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.1,"headline":"Auth bypass in RAGFlow","id":"CVE-2025-48187","kev_date_added":null,"published":"2025-05-17"},{"cvss_score":8.9,"headline":"RAGFlow SQL Injection vulnerability","id":"CVE-2025-27135","kev_date_added":null,"published":"2025-02-25"},{"cvss_score":8.8,"headline":"Remote Code Execution in infiniflow/ragflow","id":"CVE-2024-10131","kev_date_added":null,"published":"2024-10-19"},{"cvss_score":8.7,"headline":"Code injection in ragflow","id":"CVE-2026-28797","kev_date_added":null,"published":"2026-04-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-02","vendors":["infiniflow"]},"summary":"Attackers can derive API keys from shared URLs due to predictable token generation, leading to full account takeover in RAGFlow.","url":"https://insights.sbomify.com/CVE-2025-69286/"}