CVE-2026-44018

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% 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: epss, nvd
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.45.0 until 2.91.0, the METS-GBS backend's XML parsing and the input document format detection lacked security controls. An attacker could craft malicious METS-GBS archives that, when processed, could read sensitive files, exhaust system resources, or cause application crashes. This vulnerability is fixed in 2.91.0.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
1.7%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 27, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_release, github.
github Patch Available

Unsafe Archive Extraction and XML Parsing in METS-GBS Backend · Advisory · docling-project/docling · GitHub

Affected: version 2.91.0. The fix implements:

https://github.com/docling-project/docling/security/advisories/GHSA-r3xg-rg9j-67fv
github_release Patch Available

Release v2.91.0 (docling-project/docling)

Patch available: docling-project/docling v2.91.0

https://github.com/docling-project/docling/releases/tag/v2.91.0

Vendor Advisories for CVE-2026-44018(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
docling2.45.0 ... 2.90.0 (55 versions)2.91.0—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× 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-11 12:34 UTCEG score recompute
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 06:33 UTCEG score recompute
  4. 2026-07-08 16:18 UTCEG score recompute
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 19:36 UTCEG score recompute
  12. 2026-07-02 21:11 UTCEG score recompute
  13. 2026-07-02 09:20 UTCEG score recompute
  14. 2026-07-01 21:31 UTCEG score recompute
  15. 2026-07-01 09:41 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 21:50 UTCEG score recompute
  18. 2026-06-29 22:34 UTCEG score recompute
  19. 2026-06-29 10:45 UTCEG score recompute
  20. 2026-06-28 22:51 UTCEG score recompute
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 11:01 UTCEG score recompute
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 23:12 UTCEG score recompute▲ 1.60
  25. 2026-06-27 21:42 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
Show 24 more
  1. 2026-06-26 22:56 UTCEG score recompute
  2. 2026-06-25 22:35 UTCEG score recompute
  3. 2026-06-24 22:16 UTCEG score recompute
  4. 2026-06-23 18:58 UTCEG score recompute
  5. 2026-06-20 12:30 UTCEG score recompute
  6. 2026-06-19 02:44 UTCEG score recompute
  7. 2026-06-18 02:01 UTCEG score recompute
  8. 2026-06-17 01:45 UTCEG score recompute
  9. 2026-06-16 01:28 UTCEG score recompute
  10. 2026-06-15 01:11 UTCEG score recompute
  11. 2026-06-14 23:18 UTCEPSS rescore
  12. 2026-06-14 00:54 UTCEG score recompute
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 00:37 UTCEG score recompute
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 00:21 UTCEG score recompute
  17. 2026-06-11 00:05 UTCEG score recompute
  18. 2026-06-09 23:49 UTCEG score recompute
  19. 2026-06-08 23:33 UTCEG score recompute
  20. 2026-06-07 23:16 UTCEG score recompute
  21. 2026-06-06 23:00 UTCEG score recompute
  22. 2026-06-05 22:44 UTCEG score recompute
  23. 2026-06-04 22:26 UTCEG score recompute
  24. 2026-06-03 22:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44018?
CVE-2026-44018 is a high vulnerability published on June 3, 2026. Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.45.0 until 2.91.0, the METS-GBS backend's XML parsing and the input document format detection lacked security controls. An attacker could craft malicious METS-GBS…
When was CVE-2026-44018 disclosed?
CVE-2026-44018 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44018 actively exploited?
CVE-2026-44018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44018?
CVE-2026-44018 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-44018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44018, 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-44018

Explore →

Is Your Infrastructure Affected by CVE-2026-44018?

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

Start Free Scan →Browse All CVEs