Vulnerability in Docling (CVE-2026-105746)
Summary
Vulnerability in Docling (CVE-2026-105746). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.131.0 or later.
Original description
The description as published by the source.
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.83.0 until 2.131.0, the KServeV2OcrModel class defined in docling/models/stages/ocr/kserve_v2_ocr_model.py sends page images to its configured endpoint without checking the pipeline_options.enable_remote_services setting, even when the caller sets that policy control to false. The StandardPdfPipeline._make_ocr_model method also fails to pass the flag into the OCR factory, allowing remote OCR processing in configurations that rely on remote services being disabled. The destination is configured by the caller rather than selected by an attacker. This issue is fixed in 2.131.0.
Source: NIST National Vulnerability Database 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-105746 has been found in Docling.
Risk of unauthorized operations or information disclosure. CVSS score: 2.2/10.
What to do: upgrade Docling to 2.131.0 or later.
If unsure, ask your IT team or search "Docling CVE-2026-105746" on the vendor's site.
CVE-2026-105746 (Docling) — CWE-668 / CVSS v3 2.2
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.131.0 — apply immediately
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-668) exists in Docling.
Check the vendor advisory for the affected versions of Docling.
Severity: Low (CVSS 2.2/10). Risk of unauthorized operations or information disclosure.
Update to 2.131.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade Docling to 2.131.0ステージング環境で 2.131.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- patch github.com
- patch github.com