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)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
27.5%
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

Notion

https://www.notion.so/CVE-2026-31247-35d1e1393188818fa654c116c6a470bb
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
pipdocling—ghsa

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 14× in last 7d / 50× 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 148 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Same product

1 shown

pip:docling

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.5% 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.

Start Free Scan →Browse All CVEs