Docling: Unsafe URI and Path Handling in HTML Backend

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L

EPSS

• CVE-2026-47214: 0.37% estimated exploitation activity in the next 30 days; percentile 31.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The HTML backend did not perform sufficient validation during resource handling: - Accepted file:// URIs enabling local file system access when enablelocalfetch=True - Path resolution allowed traversal outside intended directories via ../ sequences and absolute paths - Did not block internal network resources under enableremotefetch=True - HTTP redirects were not validated, potentially redirecting to unintended schemes - No resource limits for remote image downloads and data: URIs Patches Fixed in versions 2.91.0 (initial fixes) and 2.94.0 (additional improvements). The fixes implement: - Updated local path treatment: absolute files always blocked, relative paths require enablelocalfetch=True (default: False) and containment within configured basepath for path traversal protection - file:// scheme stripped & treated as local path (above) - IP address validation to prevent SSRF - HTTP redirect validation, connection and read timeouts - Size limit for both remote images (with…

Published by the source

3 Jun 2026, 21:15 UTC

Last modified by the source

19 Oct 2026, 20:00 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q29v-xc37-wh5m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q29v-xc37-wh5m

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

# Patch Next advisory brief: CVE-2026-47214

Advisory: Docling: Unsafe URI and Path Handling in HTML Backend
IDs: CVE-2026-47214, GHSA-q29v-xc37-wh5m
Record: https://patchnext.com/advisories/cve-2026-47214 (revision 2, 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: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: docling 2.94.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI docling: affected < 2.94.0; fixed in 2.94.0

## 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://osv.dev/vulnerability/GHSA-q29v-xc37-wh5m (OSV record GHSA-q29v-xc37-wh5m lists affected ranges: PyPI docling >=0 <2.94.0 (fixed))
- Verified: https://github.com/advisories/GHSA-q29v-xc37-wh5m (GitHub-reviewed advisory GHSA-q29v-xc37-wh5m lists affected ranges: PyPI docling >=0 <2.94.0)

Commands are suggestions: review each one before running it.