CVE-2026-44023

HIGHPre-NVD 8.68.6
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 82% 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.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: NoneExposed: 0

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

Docling Core: Unsafe remote filename resolution

Impact

In versions >= 1.5.0, < 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner.

In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory.

Patches

Patched in docling-core 2.74.1. The fix adds stricter validation for remote destinations and normalizes server-provided filenames before use.

Users should upgrade to:

  • docling-core >= 2.74.1

Workarounds

If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.

References

CVSS v3
8.6
EG Score
8.6(low)
EPSS
17.7%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 3, 2026

Vendor Advisories for CVE-2026-44023(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-core1.5.0 ... 2.9.0 (138 versions)2.74.1—

Data Freshness Timeline

(refreshed 4× in last 7d / 40× 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 01:08 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-03 02:20 UTCEG score recompute
  7. 2026-07-02 12:27 UTCEG score recompute
  8. 2026-07-01 23:21 UTCEG score recompute
  9. 2026-07-01 10:18 UTCEG score recompute
  10. 2026-06-30 21:47 UTCEG score recompute
  11. 2026-06-29 23:15 UTCEG score recompute
  12. 2026-06-29 10:45 UTCEG score recompute
  13. 2026-06-28 17:21 UTCEG score recompute
  14. 2026-06-28 04:49 UTCEG score recompute
  15. 2026-06-27 16:18 UTCEG score recompute
  16. 2026-06-27 03:47 UTCEG score recompute
  17. 2026-06-26 15:10 UTCEG score recompute
  18. 2026-06-25 23:19 UTCEG score recompute
  19. 2026-06-25 10:49 UTCEG score recompute
  20. 2026-06-24 22:14 UTCEG score recompute
  21. 2026-06-24 09:14 UTCEG score recompute
  22. 2026-06-23 18:57 UTCEG score recompute
  23. 2026-06-20 12:30 UTCEG score recompute
  24. 2026-06-19 20:32 UTCEG score recompute
  25. 2026-06-19 05:11 UTCEG score recompute
Show 32 more
  1. 2026-06-18 16:30 UTCEG score recompute
  2. 2026-06-18 03:58 UTCEG score recompute
  3. 2026-06-17 15:26 UTCEG score recompute
  4. 2026-06-17 02:54 UTCEG score recompute
  5. 2026-06-16 14:23 UTCEG score recompute
  6. 2026-06-16 01:18 UTCEG score recompute
  7. 2026-06-15 12:48 UTCEG score recompute
  8. 2026-06-15 00:16 UTCEG score recompute
  9. 2026-06-14 23:18 UTCEPSS rescore
  10. 2026-06-14 11:45 UTCEG score recompute
  11. 2026-06-13 23:14 UTCEG score recompute
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-13 10:43 UTCEG score recompute
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 22:12 UTCEG score recompute
  16. 2026-06-12 09:40 UTCEG score recompute
  17. 2026-06-11 21:10 UTCEG score recompute
  18. 2026-06-11 08:39 UTCEG score recompute
  19. 2026-06-10 20:08 UTCEG score recompute
  20. 2026-06-10 07:37 UTCEG score recompute
  21. 2026-06-09 19:06 UTCEG score recompute
  22. 2026-06-09 06:36 UTCEG score recompute
  23. 2026-06-08 18:04 UTCEG score recompute
  24. 2026-06-08 02:41 UTCEG score recompute
  25. 2026-06-07 14:11 UTCEG score recompute
  26. 2026-06-07 01:40 UTCEG score recompute
  27. 2026-06-06 13:09 UTCEG score recompute
  28. 2026-06-06 00:38 UTCEG score recompute
  29. 2026-06-05 12:08 UTCEG score recompute
  30. 2026-06-04 23:37 UTCEG score recompute
  31. 2026-06-04 10:41 UTCEG score recompute
  32. 2026-06-03 22:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44023?
CVE-2026-44023 is a high vulnerability published on June 3, 2026. Docling Core: Unsafe remote filename resolution Impact In versions >= 1.5.0, < 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner. In applications that accept untrusted URLs, this…
When was CVE-2026-44023 disclosed?
CVE-2026-44023 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-44023 actively exploited?
CVE-2026-44023 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44023?
CVE-2026-44023 has a CVSS v4.0 base score of 8.6 (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-44023?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44023, 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-44023

Explore →

Is Your Infrastructure Affected by CVE-2026-44023?

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

Start Free Scan →Browse All CVEs