Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Docling versions 2.107.0 up to 2.120.3 (excluding 2.120.3) are affected. When converting an OpenDocument (.odt) file, the backend treats the image reference in the document as a local filesystem path, without the checks the other backends apply. An attacker who can supply a crafted .odt file can have Docling read an arbitrary local file, and if that file is an image, its contents are embedded in the conversion output. Upgrade to docling 2.120.3, which fixes the issue.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.9 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0042, the 36th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-4xhp-xg4w-8ppm
- OSV: GHSA-4xhp-xg4w-8ppm
- github.com/docling-project/docling/security/advisories/GHSA-4xhp-xg4w-8ppm
- github.com/docling-project/docling/pull/4015
- github.com/docling-project/docling/commit/6ee9965adfc364b3696a67c825ec2f0d9cee4311
- github.com/docling-project/docling
- github.com/docling-project/docling/releases/tag/v2.120.3