CVE-2026-105751: docling · Path Traversal
Affects doclingSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.120.3 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.120.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA: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-project/docling to 2.120.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| docling-projectdocling | 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
This vulnerability is fixed in docling version 2.120.3. Users should upgrade to version 2.120.3 or later to remediate this issue. No other mitigations are indicated by the vendor advisory or source data.
Description
Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.107.0 until 2.120.3, docling/backend/opendocument_backend.py uses the xlink:href attribute value of a draw:image element as a filesystem path when the referenced part is not found in the document archive. The _image_ref_from_odf_image function reads that attacker-controlled path without a scheme check, extraction-directory confinement, or the enable_local_fetch setting used by other backends. Readable files that Pillow can decode as images are embedded in converted output, and other existing paths can be distinguished through the attempted read. This issue is fixed in 2.120.3.
References
- github.com/docling-project/docling/security/advisories/GHSA-4xhp-xg4w-8ppm (opens in a new tab)
- github.com/docling-project/docling/pull/4015 (opens in a new tab)
- github.com/docling-project/docling/commit/6ee9965adfc364b3696a67c825ec2f0d9cee4311 (opens in a new tab)
- github.com/docling-project/docling/releases/tag/v2.120.3 (opens in a new tab)