Path Traversal in docling (CVE-2026-44017)
Summary
Path traversal in docling (CVE-2026-44017). Successful exploitation can lead to full system takeover. Exploitable via SecurityError. Mitigation: upgrade to 2.91.0 or later.
Original description
The description as published by the source.
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
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44017 has been found in docling.
Attackers can target a specific entry point like SecurityError over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade docling to 2.91.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-44017" on the vendor's site.
CVE-2026-44017 (docling) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: SecurityError
Patched: 2.91.0 — apply immediately
Workaround: Ensure model downloads occur over secure, authenticated channels.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in docling. Attackers reach the vulnerable code path via SecurityError without authentication.
Check the vendor advisory for the affected versions of docling. Attack surface: SecurityError.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 2.91.0.
Workaround: Ensure model downloads occur over secure, authenticated channels.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'docling' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'docling' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
doclingを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Ensure model downloads occur over secure, authenticated channels.パッチが適用されるまでの応急処置として、Ensure model downloads occur over secure, authenticated channels. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade docling to 2.91.0ステージング環境で 2.91.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web access.redhat.com
- web bugzilla.redhat.com
- web security.access.redhat.com
- web github.com
- web access.redhat.com