Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 09 Oct 2026 11:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache cxf |
|
| Weaknesses | CWE-674 | |
| Vendors & Products |
Apache
Apache cxf |
Fri, 09 Oct 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache CXF: Prevent unbounded XML document size in StaxUtils by adding default element and character limits | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-10-09T11:07:55.068Z
Reserved: 2026-10-09T09:27:04.033Z
Link: CVE-2026-108039
No data.
Status : Received
Published: 2026-10-09T11:17:02.387
Modified: 2026-10-09T11:17:02.387
Link: CVE-2026-108039
No data.
OpenCVE Enrichment
Updated: 2026-10-09T11:30:06Z