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.
Published: 2026-10-09
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Apply Patch
AI Analysis

Impact

By default, StaxUtils places no limit on the number or total characters of elements in an XML document. When Apache CXF parses large inputs—such as when building a DOM for SAAJ or WS‑Security—a very large request can consume excessive memory and CPU resources. This uncontrolled resource consumption can cripple a service and cause a denial of service. The underlying weakness is unbounded resource consumption (CWE‑770).

Affected Systems

The vulnerability affects Apache CXF releases prior to 4.2.4, 4.1.9, and 3.6.13. All deployments that use the default StaxUtils configuration are exposed because the limits are only 100× the default maximum child elements (5,000,000) and a 256‑megabyte character cap. The affected component is the XML parsing layer used by CXF applications.

Risk and Exploitability

The EPSS score is not available and the vulnerability is not listed in CISA KEV. The CVSS score of 7.5 indicates a high severity for this denial‑of‑service flaw. An adversary can exploit the flaw by sending an oversized XML payload to a CXF‑enabled service over the network. No authentication or code execution is required; the attack is performed with standard HTTP requests. The resulting high CPU and memory consumption may crash the service or deny legitimate traffic. Because the flaw is a DoS and not an arbitrary code execution, the risk level is high but the exploitation vector is straightforward.

Generated by OpenCVE AI on October 10, 2026 at 03:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to version 4.2.4, 4.1.9, or 3.6.13.
  • If immediate upgrade is not possible, set the properties org.apache.cxf.stax.maxElementCount and org.apache.cxf.stax.maxXMLCharacters to appropriate limits in the application configuration.
  • Implement network or application‑level request size restrictions to reject oversized XML payloads before they reach CXF.

Generated by OpenCVE AI on October 10, 2026 at 03:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 18:15:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:apache:cxf:*:*:*:*:*:*:*:*

Thu, 15 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-776
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 10 Oct 2026 02:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-674

Sat, 10 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important


Fri, 09 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
References

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

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-15T17:55:55.468Z

Reserved: 2026-10-09T09:27:04.033Z

Link: CVE-2026-108039

cve-icon Vulnrichment

Updated: 2026-10-09T11:07:55.068Z

cve-icon NVD

Status : Analyzed

Published: 2026-10-09T11:17:02.387

Modified: 2026-10-16T18:04:25.477

Link: CVE-2026-108039

cve-icon Redhat

Severity : Important

Publid Date: 2026-10-09T10:22:35Z

Links: CVE-2026-108039 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-10T03:30:16Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-776

    Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')