Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-105750 medium CVSS 5.9

Vulnerability in docling (CVE-2026-105750)

Summary

Vulnerability in docling (CVE-2026-105750). Confidential information can be exposed externally. Exploitable via enable_local_fetch. Mitigation: upgrade to 2.118.1 or later.

Original description

The description as published by the source.

Summary

When the HTML backend renders pages in a headless browser (HTMLBackendOptions(render_page=True)), the enable_local_fetch option is not enforced. A crafted HTML file can embed an arbitrary local file (for example with ``), and that file's contents appear in the page image attached to the returned DoclingDocument.

Details

In render mode, Playwright requests are filtered by HTMLDocumentBackend._get_browser_request_block_reason. In affected versions, this check allowed file: URLs unconditionally, before reading any option. As a result:

  • enable_local_fetch=False did not block local file access, and
  • even with enable_local_fetch=True, file access was not limited to the source document's directory, unlike the non-render path (ImageResourceLoader), which rejects absolute paths and path traversal.

Versions 2.82.0–2.90.x did no request filtering in render mode at all.

The browser runs with JavaScript disabled (from 2.91.0), so disclosure is passive: only what Chromium renders visibly inside the page viewport ends up in the page image.

Only Path inputs are affected. They are loaded through a file:// URL. Stream inputs are loaded with page.set_content() into an opaque origin, from which Chromium does not load file:// subresources.

Impact

An attacker who can submit HTML for conversion can read any text file the conversion process can read (for example .env files, credential files, or other users' documents on a shared host) by havin…

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-105750 has been found in docling.
Attackers can target a specific entry point like enable_local_fetch over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade docling to 2.118.1 or later.
If unsure, ask your IT team or search "docling CVE-2026-105750" on the vendor's site.

CVE-2026-105750 (docling) — CWE-552 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: enable_local_fetch / DoclingDocument / ImageResourceLoader / Path
Patched: 2.118.1 — apply immediately
Workaround: If you can't upgrade, don't use render_page=True on untrusted HTML, or pass the input as a stream instead of a Path.
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

A vulnerability (CWE-552) exists in docling. Attackers reach the vulnerable code path via enable_local_fetch without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of docling. Attack surface: enable_local_fetch / DoclingDocument / ImageResourceLoader / Path.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.118.1.

🛡️ Workaround

Workaround: If you can't upgrade, don't use render_page=True on untrusted HTML, or pass the input as a stream instead of a Path.

🔍 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'docling' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で docling を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    If you can't upgrade, don't use `render_page=True` on untrusted HTML, or pass the input as a stream instead of a `Path`.

    パッチが適用されるまでの応急処置として、If you can't upgrade, don't use render_page=True on untrusted HTML, or pass the input as a stream instead of a Path. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade docling to 2.118.1

    ステージング環境で 2.118.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip docling
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.118.1"}]}]
pip docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.118.1"}]}]
PyPI docling
[{"type":"ECOSYSTEM","events":[{"introduced":"2.82.0"},{"fixed":"2.118.1"}]}]
PyPI docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"2.92.0"},{"fixed":"2.118.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details