CVE-2026-53752

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% (48th percentile of EPSS-scored CVEs). 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.

docx4j is an open source Java library for creating, editing, and saving OpenXML packages, including DOCX, PPTX, and XLSX files. Prior to 11.5.14, PropertyResolver and adjacent helpers recursively follow the WordprocessingML w:basedOn style inheritance chain without cycle detection. A well-formed DOCX containing mutually based styles causes unbounded recursion in PropertyResolver.fillPPrStack and related effective-style resolution paths, resulting in StackOverflowError. Server-side conversion and table-of-contents processing of an untrusted document can terminate a worker thread, degrade a thread pool, or deny service, although isolation in disposable workers or safe containment of StackOverflowError can reduce the practical effect. The fix adds cyclic-style tracking and CyclicStylesException handling. This issue is fixed in version 11.5.14.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 17, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit.
github_commit

commit e06cafb33408 (plutext/docx4j)

Fix landed in plutext/docx4j commit e06cafb33408 — awaiting tagged release

https://github.com/plutext/docx4j/commit/e06cafb334089f0be02e1c63a7c0a602bd44bf06
github_commit

commit 47b528c7dd4c (plutext/docx4j)

Fix landed in plutext/docx4j commit 47b528c7dd4c — awaiting tagged release

https://github.com/plutext/docx4j/commit/47b528c7dd4c81bcfc8e7fe9df7610c60446f95f
github Patch Available

Stack Overflow via Cyclic `w:basedOn` Style Chain leads to Denial of Service · Advisory · plutext/docx4j · GitHub

https://github.com/plutext/docx4j/security/advisories/GHSA-gc95-3vw8-vg43

Vendor Advisories for CVE-2026-53752(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)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.docx4j:docx4j-core11.1.0 ... 8.3.9 (62 versions)
  • every version up to 11.5.14: fixed in 11.5.14
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 35× 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-10-05 11:51 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 17:45 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-02 01:33 UTCEG score recompute
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 17:51 UTCEG score recompute
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 09:56 UTCEG score recompute
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 23:58 UTCEG score recompute
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 21:37 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-27 08:04 UTCEG score recompute
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 02:23 UTCEG score recompute
  19. 2026-09-24 14:04 UTCEPSS rescore
  20. 2026-09-24 00:11 UTCEG score recompute
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-22 21:27 UTCEG score recompute
  23. 2026-09-22 08:21 UTCEG score recompute
  24. 2026-09-21 06:08 UTCEG score recompute
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 11 more
  1. 2026-09-20 02:18 UTCEG score recompute
  2. 2026-09-19 00:06 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 21:53 UTCEG score recompute
  5. 2026-09-16 16:58 UTCEG score recompute
  6. 2026-09-16 16:00 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 10:46 UTCEG score recompute
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-14 18:35 UTCEG score recompute
  11. 2026-08-17 22:02 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53752?
CVE-2026-53752 is a high vulnerability published on August 17, 2026. docx4j is an open source Java library for creating, editing, and saving OpenXML packages, including DOCX, PPTX, and XLSX files. Prior to 11.5.14, PropertyResolver and adjacent helpers recursively follow the WordprocessingML w:basedOn style inheritance chain without cycle detection. A well-formed…
When was CVE-2026-53752 disclosed?
CVE-2026-53752 was first published on August 17, 2026, with the most recent update on September 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-53752 actively exploited?
CVE-2026-53752 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53752?
CVE-2026-53752 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-53752?
A fix for CVE-2026-53752 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53752 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-53752

Explore →

Is Your Infrastructure Affected by CVE-2026-53752?

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

Book a Demo →Browse All CVEs