CVE-2026-105743: docling · Time-of-check Time-of-use (TOCTOU) Race Condition
Affects doclingSource CVE Database V5
Not known to be exploited · CVSS 4.0 Medium : upgrade to 2.132.0 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.132.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade docling and docling-slim and docling-project/docling to 2.132.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| docling-projectdocling | Affected
| Fixed in
|
| docling-projectdocling-slim | Affected
| Fixed in
|
GitHubdocling-project/doclingpkg:github/docling-project/doclingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to docling version 2.132.0 or later, where this vulnerability is fixed. Until the upgrade, remote fetching should be disabled if possible to prevent exploitation. No other specific mitigations are indicated by the vendor advisory.
Description
CVE-2026-105743 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the docling-project's docling software. Versions from 2.91.0 up to but not including 2.132.0 are affected. The issue arises because the validate_url_safety function performs a single IPv4 lookup to validate a hostname but then allows the HTTP client to resolve and parse the original URL again, enabling DNS rebinding and mixed public/internal address records to bypass validation. Additionally, HTMLBackendOptions(render_page=True) permits HTTP and HTTPS requests without validating the resolved destination. Exploitation requires remote fetching to be enabled, and the response content is only exposed when decoded as an image or rendered passively in a page screenshot. The vulnerability is fixed in version 2.132.0.
References
- github.com/docling-project/docling/security/advisories/GHSA-pc36-qwjq-x68c (opens in a new tab)
- github.com/docling-project/docling/pull/4420 (opens in a new tab)
- github.com/docling-project/docling/commit/5e469137f275ffc443306a30d12a3a45bceb80fb (opens in a new tab)
- github.com/docling-project/docling/releases/tag/v2.132.0 (opens in a new tab)