cve.bz

CVE-2026-105742 docling docling: Insufficiently Protected Credentials

5.3 mediumExploit referenceEPSS 0.3%Fix available

Medium (5.3) in docling docling. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in docling 2.132.0.

On this page
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.95.0 until 2.132.0, the HTML image resource loader in docling/backend/utils/image_resource_loader.py forwards headers configured through the HTMLBackendOptions.headers setting to every remote image URL named by an untrusted document when enable_remote_fetch=True and fetch_images=True. The loader does not restrict those credentials to the source document's origin, allowing requests that carry custom headers such as API keys and cookies to follow cross-origin redirects and expose the caller's configured credentials to a document author. The default configuration is not affected because remote fetching and configured headers are required. This issue is fixed in 2.132.0.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-201 Insertion of Sensitive Information Into Sent Data
CWE-522 Insufficiently Protected Credentials
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105742 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105742?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105742?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105742 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
docling:doclingfrom 2.95.0 before 2.132.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p3fw-7699-7926PyPIdocling>=2.95.0 <2.132.02.132.0
GHSA-p3fw-7699-7926PyPIdocling-slim>=2.95.0 <2.132.02.132.0
PYSEC-2026-4189PyPIdocling>=2.95.0 <2.132.02.132.0
PYSEC-2026-4212PyPIdocling-slim>=2.95.0 <2.132.02.132.0

Red Hat

Red Hat rates this Low.

Red Hat's statement

A LOW severity information disclosure flaw was found in docling, a document parsing and processing library. All Red Hat product streams currently tracked for this flaw, in the Ai and Portfolio business units, are affected. When docling's HTML backend is configured with remote image fetching enabled (enable_remote_fetch=True together with fetch_images=True), the HTML image resource loader forwards custom request headers configured through HTMLBackendOptions.headers — such as API keys, session tokens, and cookies — to every remote image URL referenced by a document being processed, including requests that follow cross-origin redirects. A remote attacker who supplies an untrusted document that references external images or cross-origin redirects can therefore cause the application to transmit the caller's configured authentication credentials to an attacker-controlled server. The default configuration is not affected, because exploitation requires both remote image fetching and custom headers to be explicitly enabled. Red Hat rates this flaw LOW severity (CVSS 3.1 score 3.7, vector AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N), lower than the NVD MODERATE rating (CVSS 5.3), because of the high attack complexity: exploitation depends on a non-default configuration in which remote fetching and sensitive custom headers are both enabled.

Red Hat's mitigation

Users can avoid this exposure by disabling remote image fetching in the HTML backend options (enable_remote_fetch=False), disabling image fetching altogether (fetch_images=False), or by not configuring sensitive headers such as API keys, session tokens, or cookies via HTMLBackendOptions.headers. The default docling configuration is not vulnerable because remote image fetching and configured custom headers are both required for exploitation. Updating to a release of docling that includes the upstream fix for this issue also resolves the exposure.

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-sdk-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhai-early-access/docling-serve-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-autorag-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-ogx-core-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105742.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).

References

Check your stackJSON