Vulnerability in docling (CVE-2026-44018)
Summary
Vulnerability in docling (CVE-2026-44018). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.91.0 or later.
Original description
The description as published by the source.
Impact
The METS-GBS backend's XML parsing and the input document format detection lacked security controls, enabling:
- XML External Entity (XXE) attacks to read local files or cause denial of service
- Decompression bombs (zip bombs) to exhaust memory and disk space
- Unbounded archive extraction consuming system resources
An attacker could craft malicious METS-GBS archives that, when processed, could read sensitive files, exhaust system resources, or cause application crashes.
Patches
Fixed in version 2.91.0. The fix implements:
- Secure XML parsing with
resolve_entities=False,load_dtd=False, andno_network=True - Configurable limits: 300 MB total extraction size, 10 MB per file, 1000 member count
- Cumulative size tracking across all extractions
- Early termination when limits are exceeded
- Secure format detection of METS-GBS tar archives with
_detect_mets_gbs()method: maximum file size (10 MB per file), maximum member count (1000 members), and exception handling to gracefully fail when limits are exceeded
Workarounds
Avoid processing METS-GBS archives from untrusted sources. If necessary, pre-validate archives in an isolated environment with resource limits.
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-44018 has been found in docling.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade docling to 2.91.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-44018" on the vendor's site.
CVE-2026-44018 (docling) — CWE-409 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 2.91.0 — apply immediately
Workaround: Avoid processing METS-GBS archives from untrusted sources.
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.
A vulnerability (CWE-409) exists in docling.
Check the vendor advisory for the affected versions of docling.
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.91.0.
Workaround: Avoid processing METS-GBS archives from untrusted sources.
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
Avoid processing METS-GBS archives from untrusted sources.パッチが適用されるまでの応急処置として、Avoid processing METS-GBS archives from untrusted sources. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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 github.com