Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-105742 low CVSS 3.7

Vulnerability in docling (CVE-2026-105742)

Summary

Vulnerability in docling (CVE-2026-105742). Risk of unauthorized operations or information disclosure. Exploitable via HTMLBackendOptions.headers. Mitigation: upgrade to 2.132.0 or later.

Original description

The description as published by the source.

Summary

HTMLBackendOptions.headers is documented for passing authentication headers (API keys, bearer tokens) when fetching remote images. docling sends these headers on every remote image request, to whichever host the document names. An untrusted document that references an attacker-controlled image URL receives the caller's credentials.

Details

docling/backend/utils/image_resource_loader.py merges options.headers into each remote request without checking the destination against the source document's origin. requests strips only Authorization on a cross-host redirect, so custom headers such as X-API-Key or Cookie are also forwarded across redirects.

Affected configurations

  • Affected: callers that set headers together with enable_remote_fetch=True and fetch_images=True (CLI: --html-image-headers with --html-image-fetch remote or all), and convert untrusted HTML.
  • Not affected: the default configuration.

Impact

Disclosure of the configured request headers, typically credentials, to a host chosen by the document author.

Proof of concept

Converting this file with HTMLBackendOptions(enable_remote_fetch=True, fetch_images=True, headers={"X-API-Key": "..."}) sends the key to attacker.example.

Other items from the original report (DNS validation and unvalidated browser requests) are tracked in GHSA-pc36-qwjq-x68c.

Patches

Fixed in docling 2.132.0 by [#4420](https://github.com/docling-project/docling/p…

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-105742 has been found in docling.
Attackers can target a specific entry point like HTMLBackendOptions.headers over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade docling to 2.132.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-105742" on the vendor's site.

CVE-2026-105742 (docling) — CWE-201 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: HTMLBackendOptions.headers / options.headers / requests / Authorization
Patched: 2.132.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.

❓ What is the problem

A vulnerability (CWE-201) exists in docling. Attackers reach the vulnerable code path via HTMLBackendOptions.headers without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of docling. Attack surface: HTMLBackendOptions.headers / options.headers / requests / Authorization.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.132.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 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 patch patch 
    Upgrade docling to 2.132.0

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

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

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

Affected packages

pip docling
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.132.0"}]}]
pip docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.132.0"}]}]
PyPI docling
[{"type":"ECOSYSTEM","events":[{"introduced":"2.95.0"},{"fixed":"2.132.0"}]}]
PyPI docling-slim
[{"type":"ECOSYSTEM","events":[{"introduced":"2.95.0"},{"fixed":"2.132.0"}]}]

References

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