← Back
CVE-2026-44016
high
CVSS 8.2
Code Injection in docling (CVE-2026-44016)
Summary
code injection in docling (CVE-2026-44016). Confidential information can be exposed externally. Exploitable via ``enable_remote_fetch``. Mitigation: upgrade to `2.91.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44016** has been found in docling.
Attackers can target a specific entry point like ``enable_remote_fetch`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade docling to **2.91.0** or later.
If unsure, ask your IT team or search "docling CVE-2026-44016" on the vendor's site.
CVE-2026-44016 (docling) — CWE-94 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `enable_remote_fetch`
Patched: `2.91.0` — apply immediately
Workaround: Refrain from using `render_page=True` when processing untrusted HTML documents.
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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in docling. Attackers reach the vulnerable code path via ``enable_remote_fetch`` without authentication.
📍 Affected scope
docling — . Attack surface: `enable_remote_fetch`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.91.0**.
🛡️ Workaround
Workaround: Refrain from using `render_page=True` when processing untrusted HTML documents.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Refrain from using `render_page=True` when processing untrusted HTML documents.パッチが適用されるまでの応急処置として、Refrain from using `render_page=True` when processing untrusted HTML documents. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade docling to 2.91.0ステージング環境で 2.91.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
docling
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.91.0"}]}]
PyPI
docling
[{"type":"ECOSYSTEM","events":[{"introduced":"2.82.0"},{"fixed":"2.91.0"}]}]