CVE-2026-44016: Docling: Unsafe Playwright-based HTML Rendering

Published Jun 3, 2026
·
Updated

Impact In versions >= 2.82.0, < 2.91.0, if the HTML backend was explicitly configured for rendering (rendering option by default deactivated), then the Playwright-based rendering feature could allow JavaScript execution and unrestricted network access when processing untrusted HTML documents. An attacker could craft malicious HTML that executes arbitrary JavaScript in the rendering context or makes unauthorized network requests to internal services, potentially leading to SSRF attacks, data exfiltration, or remote code execution in the rendering environment.

Patches Fixed in version 2.91.0. The rendering context now explicitly disables JavaScript execution (javascriptenabled=False) and implements network isolation controls. When enableremotefetch is disabled, the browser operates in offline mode, preventing all network requests.

Workarounds Refrain from using renderpage=True when processing untrusted HTML documents.

References - Fix release: v2.91.0

Other sources

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. FIn versions >= 2.82.0, < 2.91.0, if the HTML backend was explicitly configured for rendering (rendering option by default deactivated), then the Playwright-based rendering feature could allow JavaScript execution and unrestricted network access when processing untrusted HTML documents. An attacker could craft malicious HTML that executes arbitrary JavaScript in the rendering context or makes unauthorized network requests to internal services, potentially leading to SSRF attacks, data exfiltration, or remote code execution in the rendering environment. This vulnerability is fixed in 2.91.0.

— MITRE

Affected Software

2 affected componentsFixes available
pip/docling>=2.82.0<2.91.0
2.91.0
Docling Docling Python>=2.82.0<2.91.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/docling to a version that resolves this vulnerability.

    Fixed in 2.91.0
  2. Upgrade

    Upgrade docling to a version that resolves this vulnerability.

    Fixed in 2.91.0
  3. Configuration

    For versions >= 2.82.0 and < 2.91.0, refrain from using `render_page=True` when processing untrusted HTML documents.

    Docling HTML backend (Playwright-based rendering) render_page = false (do not use)
  4. Configuration

    Use/ensure `java_script_enabled=False` so the rendering context explicitly disables JavaScript execution (fix described for 2.91.0).

    Docling HTML backend (Playwright-based rendering) java_script_enabled = false
  5. Configuration

    Disable `enable_remote_fetch` to run the browser in offline mode, preventing all network requests.

    Docling HTML backend (Playwright-based rendering) enable_remote_fetch = false

Event History

Jun 3, 2026
Advisory Published
via GitHub·09:09 PM
Data Sourced
via GitHub·09:09 PM
DescriptionSeverityWeaknessAffected Software
Jun 24, 2026
CVE Published
via MITRE·05:42 PM
Data Sourced
via MITRE·05:42 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·06:06 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44016?

CVE-2026-44016 has a high severity rating of 8.2.

2

What impact does CVE-2026-44016 have?

CVE-2026-44016 allows for JavaScript execution and unrestricted network access when processing untrusted HTML documents in specific versions.

3

How can I protect my systems from CVE-2026-44016?

To protect against CVE-2026-44016, upgrade to a version greater than or equal to 2.91.0.

4

Which software is affected by CVE-2026-44016?

CVE-2026-44016 affects the pip/docling software in versions 2.82.0 to 2.90.9.

5

What type of vulnerability is CVE-2026-44016 classified as?

CVE-2026-44016 is classified as a Code Injection and SSRF vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203