Vulnerability in docling (CVE-2026-47214)
Summary
Vulnerability in docling (CVE-2026-47214). Confidential information can be exposed externally. Exploitable via base_path. Mitigation: upgrade to 2.94.0 or later.
Original description
The description as published by the source.
Impact
The HTML backend did not perform sufficient validation during resource handling:
- Accepted
file://URIs enabling local file system access whenenable_local_fetch=True - Path resolution allowed traversal outside intended directories via
../sequences and absolute paths - Did not block internal network resources under
enable_remote_fetch=True - HTTP redirects were not validated, potentially redirecting to unintended schemes
- No resource limits for remote image downloads and
data:URIs
Patches
Fixed in versions 2.91.0 (initial fixes) and 2.94.0 (additional improvements). The fixes implement:
- Updated local path treatment: absolute files always blocked, relative paths require
enable_local_fetch=True(default: False) and containment within configuredbase_pathfor path traversal protection file://scheme stripped & treated as local path (above)- IP address validation to prevent SSRF
- HTTP redirect validation, connection and read timeouts
- Size limit for both remote images (with streaming download) and base64-decoded data URIs
Workarounds
Keep both enable_local_fetch=False and enable_remote_fetch=False (defaults) when processing untrusted HTML documents.
References
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-47214 has been found in docling.
Attackers can target a specific entry point like base_path over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade docling to 2.94.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-47214" on the vendor's site.
CVE-2026-47214 (docling) — CWE-400 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: base_path
Patched: 2.94.0 — apply immediately
Workaround: Keep both enable_local_fetch=False and enable_remote_fetch=False (defaults) 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.
A vulnerability (CWE-400) exists in docling. Attackers reach the vulnerable code path via base_path without authentication.
Check the vendor advisory for the affected versions of docling. Attack surface: base_path.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 2.94.0.
Workaround: Keep both enable_local_fetch=False and enable_remote_fetch=False (defaults) when processing untrusted HTML documents.
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
Keep both `enable_local_fetch=False` and `enable_remote_fetch=False` (defaults) when processing untrusted HTML documents.パッチが適用されるまでの応急処置として、Keep both
enable_local_fetch=Falseandenable_remote_fetch=False(defaults) when processing untrusted HTML documents. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade docling to 2.94.0ステージング環境で 2.94.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
- web github.com