Docling: Unsafe Zip Extraction in EasyOCR Model Download

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-44017: 0.71% estimated exploitation activity in the next 30 days; percentile 53.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact In versions < 2.91.0, The EasyOCR model download functionality extracted ZIP archives without validating member paths, enabling Zip Slip attacks. If an attacker could compromise the model download source (via supply chain attack, DNS spoofing, or MITM), they could write arbitrary files to any location writable by the process, potentially achieving: - Remote code execution by overwriting Python files or system binaries - Persistent backdoors by modifying startup scripts or SSH keys - Data corruption or system compromise Patches Fixed in version 2.91.0. The extraction process now validates each archive member path using os.path.realpath() to ensure it remains within the target directory, raising a SecurityError for any path traversal attempts. Workarounds Ensure model downloads occur over secure, authenticated channels. Use integrity verification (checksums) for downloaded models. Run the application with minimal file system permissions. References - Fix release: v2.91.0

Published by the source

3 Jun 2026, 20:02 UTC

Last modified by the source

28 Aug 2026, 18:45 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cjqg-rq2h-2fvj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cjqg-rq2h-2fvj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44017

Advisory: Docling: Unsafe Zip Extraction in EasyOCR Model Download
IDs: CVE-2026-44017, GHSA-cjqg-rq2h-2fvj
Record: https://patchnext.com/advisories/cve-2026-44017 (revision 2, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: docling 2.91.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI docling: affected < 2.91.0; fixed in 2.91.0

## Suggested inspection (read-only)
- `python -m pip show docling`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on docling.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cjqg-rq2h-2fvj (OSV record GHSA-cjqg-rq2h-2fvj lists affected ranges: PyPI docling >=0 <2.91.0 (fixed))
- Verified: https://github.com/advisories/GHSA-cjqg-rq2h-2fvj (GitHub-reviewed advisory GHSA-cjqg-rq2h-2fvj lists affected ranges: PyPI docling >=0 <2.91.0)

Commands are suggestions: review each one before running it.