Quick answers
- Is CVE-2026-44016 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44016 being exploited in the wild.
- How severe is CVE-2026-44016?
- High severity, with a CVSS score of 8.2, published 24 June 2026.
- Which products and versions are affected?
- docling (PyPI) ECOSYSTEM:introduced=2.82.0,fixed=2.91.0.
- Is there a fix for CVE-2026-44016?
- Yes. docling (PyPI): upgrade to 2.91.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44016 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44016?
- Check whether you run docling (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- docling (PyPI): upgrade to 2.91.0 or later
pip install "docling>=2.91.0"
Technical details
A vulnerability exists in Docling's HTML backend (versions 2.82.0 to 2.90.x) when the optional Playwright-based rendering feature is explicitly enabled (render_page=True). The rendering context failed to disable JavaScript execution and lacked network isolation, allowing untrusted HTML documents to execute arbitrary JavaScript or perform unauthorized network requests. This can result in Server-Side Request Forgery (SSRF), data exfiltration, or code execution within the rendering environment. The issue is fixed in version 2.91.0 by disabling JavaScript in the browser context and implementing offline mode when remote fetching is disabled.
Affected products
- docling-project docling >= 2.82.0, < 2.91.0
Identifiers
- CVE-2026-44016
- GHSA-pj2v-ggqh-cmq2
- PYSEC-2026-2142
Timeline
- 2026-06-24: advisory: NVD publication date
- 2026-06-24: patched: Version 2.91.0 released with fixes