CVE-2026-44016
Received Received - Intake
Playwright JavaScript Execution in Docling HTML Rendering

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-25
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
docling docling From 2.82.0 (inc) to 2.91.0 (exc)
docling docling 2.91.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Docling versions 2.82.0 up to but not including 2.91.0 when the HTML backend rendering feature is explicitly enabled. It involves the Playwright-based rendering feature which can execute JavaScript and allow unrestricted network access while processing untrusted HTML documents.

An attacker can craft malicious HTML that executes arbitrary JavaScript within the rendering context or makes unauthorized network requests to internal services.

This can lead to server-side request forgery (SSRF) attacks, data exfiltration, or even remote code execution within the rendering environment.

Impact Analysis

The vulnerability can have serious impacts including unauthorized execution of JavaScript code, which may compromise the security of the system processing the documents.

  • Potential for SSRF attacks allowing attackers to access internal services.
  • Risk of data exfiltration through malicious network requests.
  • Possibility of remote code execution in the rendering environment, leading to further system compromise.
Mitigation Strategies

To mitigate this vulnerability, upgrade Docling to version 2.91.0 or later, where the issue is fixed.

Additionally, avoid enabling the HTML backend rendering feature with Playwright for untrusted HTML documents, as this feature allows JavaScript execution and unrestricted network access.

Compliance Impact

This vulnerability allows execution of arbitrary JavaScript and unrestricted network access when processing untrusted HTML documents, potentially leading to data exfiltration and unauthorized network requests.

Such risks could impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive data against unauthorized access and exfiltration.

Specifically, the potential for data exfiltration and remote code execution could lead to breaches of confidentiality and integrity, violating regulatory requirements for protecting personal and health information.

Detection Guidance

This vulnerability occurs when the Docling library versions 2.82.0 to 2.90.0 are used with the HTML backend explicitly configured for rendering (using the render_page=True option). Detection involves identifying if your system or network is running a vulnerable version of Docling with this configuration enabled.

To detect potential exploitation or presence of this vulnerability, you can:

  • Check the installed Docling version to see if it falls within the vulnerable range (2.82.0 to 2.90.0). For example, run: `pip show docling` or `pip list | grep docling`.
  • Audit your application code or configuration for usage of the `render_page=True` option when processing HTML documents.
  • Monitor network traffic for unusual outbound requests originating from the Docling rendering process, which could indicate exploitation attempts involving JavaScript execution or SSRF.

Specific commands to help detect the vulnerability or its exploitation might include:

  • Listing installed Docling version: `pip show docling`
  • Searching code for render_page usage: `grep -r 'render_page=True' /path/to/your/code`
  • Monitoring network connections from the Docling process (example for Linux): `sudo netstat -tunp | grep python` or `sudo lsof -i -a -p $(pgrep -f docling)`
  • Using packet capture tools like tcpdump or Wireshark to analyze suspicious outbound HTTP requests during document processing.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44016. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart