CVE-2026-44020

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% 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, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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.13.0 until 2.74.0, the USPTO patent XML parser used the standard xml.sax.parseString() without protection against XML External Entity (XXE) attacks. An attacker could craft malicious USPTO patent XML files with external entity references that could read arbitrary files from the server filesystem, perform Server-Side Request Forgery (SSRF) attacks, or cause denial of service through entity expansion (Billion Laughs attack). The vulnerability affects three USPTO patent format parsers: ICE (v4.x), Grant v2.5, and Application v1.x. This vulnerability is fixed in 2.74.0.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
25.4%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 30, 2026

Advisory Details (1)

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

Unsafe XML Entity Expansion in USPTO Patent Backend · Advisory · docling-project/docling · GitHub

Affected: version 2.74.0. The parser now uses

https://github.com/docling-project/docling/security/advisories/GHSA-m88r-rg27-5xfg

Vendor Advisories for CVE-2026-44020(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.13.0 ... 2.73.1 (84 versions)2.74.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-44020?
CVE-2026-44020 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.13.0 until 2.74.0, the USPTO patent XML parser used the standard xml.sax.parseString() without protection against XML External Entity (XXE) attacks. An attacker…
When was CVE-2026-44020 disclosed?
CVE-2026-44020 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44020 actively exploited?
CVE-2026-44020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44020?
CVE-2026-44020 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44020, 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-44020

Explore →

Is Your Infrastructure Affected by CVE-2026-44020?

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

Start Free Scan →Browse All CVEs