Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-53752 high CVSS 7.5

Vulnerability in org.docx4j:docx4j-core (CVE-2026-53752)

Summary

Vulnerability in org.docx4j:docx4j-core (CVE-2026-53752). Risk of unauthorized operations or information disclosure. Exploitable via PropertyResolver. Mitigation: upgrade to 11.5.14 or later.

Original description

The description as published by the source.

Summary

docx4j's PropertyResolver and several adjacent helpers recursively walk the OpenXML style inheritance chain (w:basedOn) without cycle detection.

A WordprocessingML document containing a cyclic style chain (for example, Style A based on B and Style B based on A) causes unbounded recursion and a java.lang.StackOverflowError within the property-resolution code path.

These helpers are used by operations that require effective style resolution, including common conversion and TOC-related paths. As a result, most server-side pipelines that accept a user-supplied docx and process it through docx4j can likely be crashed by a file containing a cyclic style reference.

Details

Representative snippet: PropertyResolver.fillPPrStack

private void fillPPrStack(String styleId, Stack pPrStack) {
    Style style = liveStyles.get(styleId);
    ...
    // if it is based on, recurse
    if (style.getBasedOn() == null) {
        log.debug("Style " + styleId + " is a root style.");
    } else if (style.getBasedOn().getVal() != null) {
        String basedOnStyleName = style.getBasedOn().getVal();
        fillPPrStack(basedOnStyleName, pPrStack);   // ← unbounded recursion
        ...

Impact

This is a denial of service against a server-side application that processes untrusted docx files via docx4j.

An upload causes the processing thread to be terminated with StackOverflowError which may crash the worker thread, degrade the thread pool, or evade nor…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-53752 has been found in org.docx4j:docx4j-core.
Attackers can target a specific entry point like PropertyResolver over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.docx4j:docx4j-core to 11.5.14 or later.
If unsure, ask your IT team or search "org.docx4j:docx4j-core CVE-2026-53752" on the vendor's site.

CVE-2026-53752 (org.docx4j:docx4j-core) — CWE-674 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PropertyResolver / java.lang.StackOverflowError / PropertyResolver.fillPPrStack / StackOverflowError
Patched: 11.5.14 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-674) exists in org.docx4j:docx4j-core. Attackers reach the vulnerable code path via PropertyResolver without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.docx4j:docx4j-core. Attack surface: PropertyResolver / java.lang.StackOverflowError / PropertyResolver.fillPPrStack / StackOverflowError.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 11.5.14.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.docx4j:docx4j-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.docx4j:docx4j-core to 11.5.14

    ステージング環境で 11.5.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.docx4j:docx4j-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.5.14"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details