dbcve.org
RagflowApplication · Infiniflow

CVE-2026-24770

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to after 0.23.1 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 version 0.23.1 and possibly earlier versions, the MinerU parser contains a "Zip Slip" vulnerability, allowing an attacker to overwrite arbitrary files on the server (leading to Remote Code Execution) via a malicious ZIP archive. The MinerUParser class retrieves and extracts ZIP files from an external source (mineru_server_url). The extraction logic in `_extract_zip_no_root` fails to sanitize filenames within the ZIP archive. Commit 64c75d558e4a17a4a48953b4c201526431d8338f contains a patch for 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's MinerU parser contains a Zip Slip vulnerability (CWE-22) in the `_extract_zip_no_root` method. The extraction logic fails to sanitize filenames containing path traversal sequences (../) within ZIP archives, allowing attackers to write files outside the intended extraction directory. This enables arbitrary file overwrite leading to Remote Code Execution.

MitigationApply the patch from commit 64c75d558e4a17a4a48953b4c201526431d8338f or upgrade to a fixed version. Until patched, do not process untrusted ZIP files through the MinerUParser from untrusted min eru_server_url sources.

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.23.1

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 Ragflow version
    Check the installed Ragflow version (e.g., via Docker image tag, git tag, or version file in the installation directory). Compare against the affected range: <= 0.23.1
    Affected if Installed version is 0.23.1 or earlier
  2. Locate the vulnerable parser code
    Search the codebase for the _extract_zip_no_root method, typically found in parser-related Python files under the MinerU or parser modules
    Affected if The method exists and contains extraction logic without path traversal sanitization
  3. Check for path traversal safeguards
    Inspect the _extract_zip_no_root method for sanitization of '../' sequences in filenames extracted from ZIP archives
    Affected if No sanitization of '../' or '..\' sequences is present in the extraction logic
  4. Identify MinerUParser exposure
    Check if the MinerUParser is enabled and exposed via API or web interface, particularly checking configurations that accept ZIP file uploads for processing
    Affected if MinerUParser is active and processes ZIP files from external or untrusted sources
  5. Verify ZIP processing configuration
    Review server configuration files for settings related to min eru_server_url (or minerU_server_url) and ZIP file handling
    Affected if The parser is configured to process ZIP files from untrusted or external sources without additional validation

A user is affected if they are running Ragflow version 0.23.1 or earlier and the MinerUParser is enabled to process ZIP files, with the _extract_zip_no_root method lacking path traversal sanitization.

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 a release after 0.23.1
Vendor patch github.com →
Interim mitigation

Apply the patch from commit 64c75d558e4a17a4a48953b4c201526431d8338f or upgrade to a fixed version. Until patched, do not process untrusted ZIP files through the MinerUParser from untrusted min eru_server_url sources.

Recommended fix Moderate confidence

ragflow > 0.23.1 (latest available version)

  1. 1. Identify your current Ragflow version by checking the deployment configuration or the running container/image tag.
  2. 2. If you are running Ragflow version 0.23.1 or earlier, plan to upgrade to a newer version.
  3. 3. Pull the latest Ragflow Docker image or update your deployment to use a version newer than 0.23.1.
  4. 4. Deploy the upgraded version and verify the service starts successfully.
  5. 5. Test the MinerU parser functionality to ensure the update does not break expected behavior.
  6. 6. If you cannot upgrade immediately, you may manually apply the fix by reviewing commit 64c75d558e4a17a4a48953b4c201526431d8338f and modifying the `_extract_zip_no_root` method in the MinerUParser class to properly sanitize filenames within ZIP archives before extraction, ensuring extracted files cannot escape the target directory.

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

Fix this in Ragflow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24770 — 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-2026-24770 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