CVE-2026-31247

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-11. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks thru 2.61.0. The backend uses etree.parse() to parse XML files without disabling entity resolution. An attacker can craft a malicious XML file containing a nested entity expansion payload (XML Bomb). When processed by Docling, the exponential expansion of entities leads to excessive resource consumption, resulting in a denial of service (DoS) condition on the system running the Docling parser.

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

Published

May 11, 2026

Last Modified

May 13, 2026

Advisory Details (2)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

GitHub - docling-project/docling: Get your documents ready for gen AI · GitHub

https://github.com/docling-project/docling

Vendor Advisories for CVE-2026-31247(1)

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 / EcosystemFixed in / PatchReleasedSource
pipdoclingghsa

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 rangeFixed inDependents
docling0.1.0 ... 2.9.0 (137 versions)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 64× 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 163 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31247?
CVE-2026-31247 is a high vulnerability published on May 11, 2026. Docling's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks thru 2.61.0. The backend uses etree.parse() to parse XML files without disabling entity resolution. An attacker can craft a malicious XML file containing a nested entity expansion payload (XML Bomb). When processed by…
When was CVE-2026-31247 disclosed?
CVE-2026-31247 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31247 actively exploited?
CVE-2026-31247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31247?
CVE-2026-31247 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31247, 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-31247

Explore →

Is Your Infrastructure Affected by CVE-2026-31247?

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