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

QFinch assessment

When the HTML backend renders pages in a headless browser (HTMLBackendOptions(renderpage=True)), the enablelocalfetch 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.

Potential 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(renderpage=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 (renderpage=False), the docling CLI, docling-serve, and the EPUB, Markdown, XBRL and email backends.

Technical context

In render mode, Playwright requests are filtered by HTMLDocumentBackend.getbrowserrequestblockreason. In affected versions, this check allowed file: URLs unconditionally, before reading any option. As a result: - enablelocalfetch=False did not block local file access, and - even with enablelocalfetch=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.setcontent() into an opaque origin, from which Chromium does not load file:// subresources.