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.6%, top 53% 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

Published

June 3, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

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(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-autorag-rhel9:17866126372026-08-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
docling2.13.0 ... 2.73.1 (84 versions)
  • 2.13.0 up to 2.74.0: fixed in 2.74.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 24× 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.

Showing the most recent 100 of 127 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-03 12:09 UTCOSV refresh
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-23 17:53 UTCEPSS rescore
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-17 19:31 UTCEPSS rescore
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-14 05:29 UTCEG score recompute
  19. 2026-09-14 05:29 UTCVendor advisory
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-12 15:01 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-08 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-28 16:46 UTCEG score recompute
  10. 2026-08-28 16:46 UTCVendor advisory
  11. 2026-08-28 15:59 UTCEG score recompute
  12. 2026-08-28 15:59 UTCVendor advisory
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-25 03:36 UTCEG score recompute
  17. 2026-08-23 12:45 UTCEG score recompute
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 14:40 UTCEG score recompute
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 10:00 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
  26. 2026-08-16 15:29 UTCEG score recompute
  27. 2026-08-16 14:56 UTCEPSS rescore
  28. 2026-08-16 03:04 UTCEG score recompute
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 14:39 UTCEG score recompute
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-13 22:49 UTCEG score recompute
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-12 14:17 UTCEG score recompute
  35. 2026-08-12 13:51 UTCEPSS rescore
  36. 2026-08-12 01:52 UTCEG score recompute
  37. 2026-08-11 13:43 UTCEPSS rescore
  38. 2026-08-11 00:58 UTCEG score recompute
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-09 23:56 UTCEG score recompute
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-08 23:05 UTCEG score recompute
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-07 22:11 UTCEG score recompute
  45. 2026-08-06 21:21 UTCEG score recompute
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-05 20:31 UTCEG score recompute
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 19:18 UTCEG score recompute
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:38 UTCEPSS rescore
  52. 2026-08-03 15:42 UTCEG score recompute
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 13:52 UTCEG score recompute
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 13:02 UTCEG score recompute
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-31 05:30 UTCEG score recompute
  59. 2026-07-30 16:28 UTCEPSS rescore
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-29 10:17 UTCEG score recompute
  62. 2026-07-28 15:36 UTCEPSS rescore
  63. 2026-07-28 03:29 UTCEG score recompute
  64. 2026-07-27 14:13 UTCEPSS rescore
  65. 2026-07-26 22:29 UTCEG score recompute
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-23 14:18 UTCEPSS rescore
  71. 2026-07-23 03:14 UTCEG score recompute
  72. 2026-07-22 14:08 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 02:29 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

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 on June 3, 2026, with the most recent update on August 28, 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 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44020?
CVE-2026-44020 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44020?
A fix for CVE-2026-44020 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44020 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs