CVE-2026-44016

Workarounds

Refrain from using render_page=True when processing untrusted HTML documents.

References

• Fix release: v2.91.0

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.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2026-44016 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.91.0); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-44016? CVE-2026-44016 is a high-severity code injection vulnerability in docling (pip), affecting versions >= 2.82.0, < 2.91.0. It is fixed in 2.91.0. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2026-44016? CVE-2026-44016 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of docling are affected by CVE-2026-44016? docling (pip) versions >= 2.82.0, < 2.91.0 is affected.
4. Is there a fix for CVE-2026-44016? Yes. CVE-2026-44016 is fixed in 2.91.0. Upgrade to this version or later.
5. Is CVE-2026-44016 exploitable, and should I be worried? Whether CVE-2026-44016 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-44016 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-44016? Upgrade docling to 2.91.0 or later.