GHSA-q43m-vhcp-mhvm

Source

https://github.com/advisories/GHSA-q43m-vhcp-mhvm

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-q43m-vhcp-mhvm/GHSA-q43m-vhcp-mhvm.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-q43m-vhcp-mhvm

Aliases

CVE-2026-105750

Published

2026-10-06T00:02:27Z

Modified

2026-10-06T00:15:12Z

Severity

5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator

Summary

Docling: `enable_local_fetch` is not enforced in HTML browser-rendering mode

Details

Summary

When the HTML backend renders pages in a headless browser (HTMLBackendOptions(render_page=True)), the enable_local_fetch option is not enforced. A crafted HTML file can embed an arbitrary local file (for example with <iframe src="file:///...">), and that file's contents appear in the page image attached to the returned DoclingDocument.

Details

In render mode, Playwright requests are filtered by HTMLDocumentBackend._get_browser_request_block_reason. In affected versions, this check allowed file: URLs unconditionally, before reading any option. As a result:

enable_local_fetch=False did not block local file access, and
even with enable_local_fetch=True, file access was not limited to the source document's directory, unlike the non-render path (ImageResourceLoader), which rejects absolute paths and path traversal.

Versions 2.82.0–2.90.x did no request filtering in render mode at all.

The browser runs with JavaScript disabled (from 2.91.0), so disclosure is passive: only what Chromium renders visibly inside the page viewport ends up in the page image.

Only Path inputs are affected. They are loaded through a file:// URL. Stream inputs are loaded with page.set_content() into an opaque origin, from which Chromium does not load file:// subresources.

Impact

An attacker who can submit HTML for conversion can read any text file the conversion process can read (for example .env files, credential files, or other users' documents on a shared host) by having it rendered into the page image.

Only applications that meet all of these conditions are affected:

they set HTMLBackendOptions(render_page=True) in Python,
they have the optional playwright dependency installed, and
they pass untrusted HTML as a filesystem Path.

The following are not affected: the default configuration (render_page=False), the docling CLI, docling-serve, and the EPUB, Markdown, XBRL and email backends.

Patches

Fixed in 2.118.1 (#3948). In render mode, file: requests are now blocked unless enable_local_fetch=True, and allowed requests are limited to the source document's directory.

Workarounds

If you can't upgrade, don't use render_page=True on untrusted HTML, or pass the input as a stream instead of a Path.

Credits

Reported by @priyankn.

Database specific

{
    "cwe_ids": [
        "CWE-552",
        "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-06T00:02:27Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
}

References

Affected packages

PyPI / docling

Package

Name: docling; View open source insights on deps.dev
Purl: pkg:pypi/docling

Affected ranges

Type: ECOSYSTEM
Events: Introduced

2.82.0

Fixed

2.118.1

Affected versions

2.*

2.82.0

2.83.0

2.84.0

2.85.0

2.86.0

2.87.0

2.88.0

2.89.0

2.90.0

2.91.0

2.92.0

2.93.0

2.94.0

2.95.0

2.96.0

2.96.1

2.97.0

2.98.0

2.99.0

2.100.0

2.101.0

2.102.0

2.102.1

2.102.2

2.103.0

2.104.0

2.105.0

2.106.0

2.107.0

2.108.0

2.109.0

2.110.0

2.111.0

2.112.0

2.113.0

2.114.0

2.115.0

2.116.0

2.117.0

2.118.0

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-q43m-vhcp-mhvm/GHSA-q43m-vhcp-mhvm.json"

PyPI / docling-slim