CVE-2026-44019
Local file read and memory exhaustion via image refs in docling-core <=2.74.0
Is CVE-2026-44019 being exploited?
Not confirmed. CVE-2026-44019 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-44019?
CVE-2026-44019 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44019?
Yes. A fix has been recorded for CVE-2026-44019. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44019 affect?
CVE-2026-44019 affects Docling Core 2.5.0 through 2.74.0, Applications using docling-core that accept untrusted image refs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44019?
Upgrade docling-core to >=2.74.1; block/validate file:// and large data: URIs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows file:// image refs to read local files and unbounded data: payloads to exhaust memory (local file disclosure and DoS).
Patch when possible
- affected>= 2.5.0 and < 2.74.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.