{"answers":{"affected":"2 open source packages ship an affected version, including org.docx4j:docx4j-core.","exploited":"There is no known exploitation of CVE-2026-53752 in the wild and no public exploit code.","fix":"Upgrade org.docx4j:docx4j-core to 11.5.14 or later.","what":"CVE-2026-53752 is a high-severity denial of service vulnerability in org.docx4j docx4j, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53752 and fix it if it is affected.\n\nWhat it is: CVE-2026-53752 is a high-severity denial of service vulnerability in org.docx4j docx4j, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53752 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.docx4j:docx4j-core (Maven): affected all versions; fixed in 11.5.14\n- org.docx4j:docx4j-core (Maven): affected all versions; fixed in 11.5.14\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53752/ (Markdown: https://insights.sbomify.com/CVE-2026-53752/index.md)","id":"CVE-2026-53752","markdown":"https://insights.sbomify.com/CVE-2026-53752/index.md","name":"CVE-2026-53752","record":{"aliases":["GHSA-gc95-3vw8-vg43"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java document library","requires_auth":"none","summary":"Attackers can cause denial of service in applications using docx4j by submitting DOCX files with cyclic style definitions, triggering stack overflow errors.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"docx4j: Stack Overflow via Cyclic `w:basedOn` Style Chain leads to Denial of Service","id":"CVE-2026-53752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API","id":"CVE-2026-53753"},"packages":[{"ecosystem":"Maven","fixed":["11.5.14"],"introduced":["0"],"last_affected":[],"package":"org.docx4j:docx4j-core","purl":null,"source":"GHSA-gc95-3vw8-vg43"},{"ecosystem":"Maven","fixed":["11.5.14"],"introduced":["0"],"last_affected":[],"package":"org.docx4j:docx4j-core","purl":"pkg:maven/org.docx4j/docx4j-core","source":"GHSA-gc95-3vw8-vg43"}],"prev":{"headline":"DataEase: H2 JDBC URL Filter Bypass Leads to Remote Code Execution (RCE)","id":"CVE-2026-53751"},"products":["docx4j","docx4j-core"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["org.docx4j","plutext"]},"summary":"Attackers can cause denial of service in applications using docx4j by submitting DOCX files with cyclic style definitions, triggering stack overflow errors.","url":"https://insights.sbomify.com/CVE-2026-53752/"}