Advisory [CVE-2026-108039] By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML document
This security Apache Software Foundation advisory covers CVE-2026-108039; related products: Apache CXF.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML document.
A very large request could therefore use a lot of memory and CPU during parsing, especially where CXF builds a DOM from the input (for example SAAJ or WS-Security), and could cause a denial of service when no request size limit was configured.
Both limits now have defaults: the maximum element count is 100 × maxChildElements (5,000,000 by default), and the maximum document size is 256M characters. Applications that process larger documents can raise the limits with the org.apache.cxf.stax.maxElementCount and org.apache.cxf.stax.maxXMLCharacters properties.
Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
- Apache CXF 4.2.0 before 4.2.4
- Apache CXF 4.0.0 before 4.1.9
- Apache CXF before 3.6.13
Official advisory · medium-confidence parse· fetched 16 hours ago·verify at source
- 4.2.4
- 4.1.9
- 3.6.13
Official advisory · medium-confidence parse· fetched 16 hours ago·verify at source
Mitigation checklist
- By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML document.
- A very large request could therefore use a lot of memory and CPU during parsing, especially where CXF builds a DOM from the input (for example SAAJ or WS-Security), and could cause a denial of service when no request size limit was configured.
- Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Official advisory · medium-confidence parse· fetched 16 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.