CVE-2026-44019

HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Docling Core: Insufficient validation of image reference URIs

Impact

In versions >= 2.5.0, < 2.74.1, docling-core could allow local file:// image references and accepted inline data: content without a decoded-size limit.

In applications that accept untrusted image references, this may allow access to local files readable by the process or excessive memory use from large inline payloads.

Patches

Patched in docling-core 2.74.1. The fix blocks local file URIs by default and adds a size limit for decoded inline image data.

Users should upgrade to:

  • docling-core >= 2.74.1

Workarounds

If upgrading is not immediately possible:
  • reject file: and data: image references from untrusted input
  • allow only approved local or remote image sources
  • apply input size and memory limits to processing workers

References

CVSS v3
8.1
EG Score
8.1(low)
EPSS
12.6%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 3, 2026

Vendor Advisories for CVE-2026-44019(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
docling-core2.10.0 ... 2.9.0 (118 versions)2.74.1—

Data Freshness Timeline

(refreshed 4× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 00:29 UTCEG score recompute
  2. 2026-07-11 12:34 UTCEG score recompute
  3. 2026-07-09 06:31 UTCEG score recompute
  4. 2026-07-08 16:18 UTCEG score recompute
  5. 2026-07-03 19:35 UTCEG score recompute
  6. 2026-07-02 21:42 UTCEG score recompute
  7. 2026-07-02 09:47 UTCEG score recompute
  8. 2026-07-01 21:52 UTCEG score recompute
  9. 2026-07-01 09:55 UTCEG score recompute
  10. 2026-06-30 21:50 UTCEG score recompute
  11. 2026-06-30 02:40 UTCEG score recompute
  12. 2026-06-29 14:45 UTCEG score recompute
  13. 2026-06-29 02:50 UTCEG score recompute
  14. 2026-06-28 14:54 UTCEG score recompute
  15. 2026-06-28 02:56 UTCEG score recompute
  16. 2026-06-27 15:01 UTCEG score recompute
  17. 2026-06-27 03:06 UTCEG score recompute
  18. 2026-06-26 15:10 UTCEG score recompute
  19. 2026-06-25 22:35 UTCEG score recompute
  20. 2026-06-25 10:36 UTCEG score recompute
  21. 2026-06-24 22:14 UTCEG score recompute
  22. 2026-06-24 09:14 UTCEG score recompute
  23. 2026-06-23 18:57 UTCEG score recompute
  24. 2026-06-20 12:30 UTCEG score recompute
  25. 2026-06-19 20:32 UTCEG score recompute
Show 34 more
  1. 2026-06-18 21:31 UTCEG score recompute
  2. 2026-06-18 07:51 UTCEG score recompute
  3. 2026-06-17 19:55 UTCEG score recompute
  4. 2026-06-17 08:00 UTCEG score recompute
  5. 2026-06-16 20:05 UTCEG score recompute
  6. 2026-06-16 08:10 UTCEG score recompute
  7. 2026-06-15 20:15 UTCEG score recompute
  8. 2026-06-15 08:19 UTCEG score recompute
  9. 2026-06-14 23:18 UTCEPSS rescore
  10. 2026-06-14 20:20 UTCEG score recompute
  11. 2026-06-14 08:26 UTCEG score recompute
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-13 20:31 UTCEG score recompute
  14. 2026-06-13 08:34 UTCEG score recompute
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 20:38 UTCEG score recompute
  17. 2026-06-12 08:43 UTCEG score recompute
  18. 2026-06-11 20:49 UTCEG score recompute
  19. 2026-06-11 08:54 UTCEG score recompute
  20. 2026-06-10 20:59 UTCEG score recompute
  21. 2026-06-10 09:05 UTCEG score recompute
  22. 2026-06-09 21:10 UTCEG score recompute
  23. 2026-06-09 09:16 UTCEG score recompute
  24. 2026-06-08 21:21 UTCEG score recompute
  25. 2026-06-08 09:21 UTCEG score recompute
  26. 2026-06-07 21:27 UTCEG score recompute
  27. 2026-06-07 09:33 UTCEG score recompute
  28. 2026-06-06 21:38 UTCEG score recompute
  29. 2026-06-06 09:43 UTCEG score recompute
  30. 2026-06-05 21:49 UTCEG score recompute
  31. 2026-06-05 09:55 UTCEG score recompute
  32. 2026-06-04 22:00 UTCEG score recompute
  33. 2026-06-04 10:05 UTCEG score recompute
  34. 2026-06-03 22:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44019?
CVE-2026-44019 is a high vulnerability published on June 3, 2026. Docling Core: Insufficient validation of image reference URIs Impact In versions >= 2.5.0, < 2.74.1, docling-core could allow local file:// image references and accepted inline data: content without a decoded-size limit. In applications that accept untrusted image references, this may allow access…
When was CVE-2026-44019 disclosed?
CVE-2026-44019 was first published in the National Vulnerability Database on June 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44019 actively exploited?
CVE-2026-44019 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44019?
CVE-2026-44019 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-44019?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44019, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44019

Explore →

Is Your Infrastructure Affected by CVE-2026-44019?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs