Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend

CVE-2026-105751GHSA-4xhp-xg4w-8ppm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (docling 2.120.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI docling

    Affected
    >= 2.107.0, < 2.120.3
    Fixed in
    2.120.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · 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 · score source
EPSS
  • CVE-2026-105751: 0.42% estimated exploitation activity in the next 30 days; percentile 36.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The ODF backend resolves the xlink:href of a draw:image element as a filesystem path whenever the referenced part is not found inside the document archive. The value comes straight from content.xml, so it is document content, and it is used with no scheme check, no confinement to the extraction directory, and without consulting the enablelocalfetch / enableremotefetch controls that the other backends use for exactly this decision. Converting a crafted .odt therefore causes Docling to open an attacker-named absolute path on the converting host. Where the target decodes as an image, its complete contents are embedded in the resulting DoclingDocument and appear in the HTML, Markdown and JSON exports. Both the read and the disclosure are confirmed by execution. The trigger is a 452-byte archive containing two entries. Affected component docling/backend/opendocumentbackend.py, in imagereffromodfimage: odfimagehref returns the xlink:href attribute. The in-archive lookup is…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-4xhp-xg4w-8ppm

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-4xhp-xg4w-8ppm

  4. Revision 1 · created ·

    Published from ghsa record GHSA-4xhp-xg4w-8ppm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-105751

Advisory: Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend
IDs: CVE-2026-105751, GHSA-4xhp-xg4w-8ppm
Record: https://patchnext.com/advisories/cve-2026-105751 (revision 4, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: docling 2.120.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI docling: affected >= 2.107.0, < 2.120.3; fixed in 2.120.3

## Suggested inspection (read-only)
- `python -m pip show docling`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on docling.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4xhp-xg4w-8ppm (GitHub-reviewed advisory GHSA-4xhp-xg4w-8ppm lists affected ranges: PyPI docling >=2.107.0 <2.120.3)
- Verified: https://osv.dev/vulnerability/GHSA-4xhp-xg4w-8ppm (OSV record GHSA-4xhp-xg4w-8ppm lists affected ranges: PyPI docling >=2.107.0 <2.120.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…