INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-105750

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

CVE-2026-105750 · 2026-10-06 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Information exposure
Affected
docling (PyPI)
Gets past
Path restriction
CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

In browser render mode a crafted HTML page embeds local file URLs that were allowed unconditionally, so local file contents appear in the rendered page image. (Our summary, written by a model. The source text is below.)

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:

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:

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.