Apache CXF header size limits bypass allows memory exhaustion
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Partial Red Hat: 1 fixed, 6 without a fix
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and Red Hat. Impact type from CWE-770.
Summary
Apache CXF versions from 4.2.0 before 4.2.4, from 4.0.0 before 4.1.9, and before 3.6.13 are affected. The parser for multipart and MTOM attachment headers does not fully enforce its configured size and count limits, a missing resource limit (CWE-770). A remote, unauthenticated attacker can send a multipart request with very large folded or repeated part headers, which makes the server allocate memory without bound and causes a denial of service.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the configured attachment-max-header-size (default 300 characters) and attachment-headers-max-count (default 500) limits. The size limit was applied only to each physical line, not to a header value built from continuation lines or to the combined values of a repeated header. The count limit was checked against the number of distinct header names, not the total number of header lines. A remote, unauthenticated attacker could send a multipart request with very large folded or repeated part headers. The server would then allocate memory without bound, causing a denial of service. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Apache | Apache CXF | 4.2.0 to before 4.2.4; 4.0.0 to before 4.1.9; before 3.6.13 | 4.2.4, 4.1.9, 3.6.13 | Patch available | CNA |
- Apache CXF VendorApache Affected 4.2.0 to before 4.2.4; 4.0.0 to before 4.1.9; before 3.6.13 Fixed in 4.2.4, 4.1.9, 3.6.13 Patch available CNA
Remediation
Upgrade to Apache CXF 4.2.4, 4.1.9 or 3.6.13. Red Hat advisory RHSA-2026:95622 fixes Red Hat Build of Apache Camel 3.33.4.SP3. The sources list no fixed version for JBoss Enterprise Application Platform 7, JBoss Web Server 5, Single Sign-On 7, JBoss Enterprise Application Platform 8, Red Hat build of Apache Camel 4 for Quarkus 3 and Red Hat build of Apache Camel for Spring Boot 4.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA Apache CXF (Apache Software Foundation) Fixed in 4.2.4, 4.1.9, 3.6.13
Red Hat 1 advisory
- RHSA-2026:95622 Released 2026-11-05 · Red Hat rating ImportantRed Hat Build of Apache Camel 4.18 for Quarkus 3.33 update is now available (RHBQ 3.33.4.SP3)
- Red Hat Build of Apache Camel 3.33.4.SP3 com.google.guava.guava-33.7.2.jre-redhat-00002.jar, io.vertx.vertx-grpc-server-4.5.35.redhat-00001.jar, io.vertx.vertx-web-4.5.35.redhat-00001.jar +4
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache CXF 3.6.13, 4.1.9, 4.2.4
11 records Highest priority Priority MEDIUM 4 MEDIUM, 7 LOW
Other records, highest priority first
- TI-2026-69970 Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.Priority MEDIUM 47
- TI-2026-69966 Authentication bypass in Apache CXF via weak STS token cache keysPriority MEDIUM 47
- TI-2026-69961 Apache CXF OIDC max_age check accepts sessions of any agePriority MEDIUM 47
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7 | Affected | No fix planned: Out of support scope |
| Red Hat JBoss Enterprise Application Platform 8 | Affected | No fix yet |
| Red Hat JBoss Web Server 5 | Affected | No fix planned: Out of support scope |
| Red Hat Single Sign-On 7 | Affected | No fix planned: Will not fix |
| Red Hat build of Apache Camel 4 for Quarkus 3 | Affected | No fix yet |
| Red Hat build of Apache Camel for Spring Boot 4 | Affected | No fix yet |
| Red Hat Build of Apache Camel 3.33.4.SP3 | Fixed | RHSA-2026:95622 |
Not affected: 3 products
- Red Hat Build of Apache Camel 3.33.4.SP3
- Red Hat Fuse 7
- Red Hat JBoss Enterprise Application Platform Expansion Pack
Timeline
- 2026-10-09 Threatist record created from CVE-2026-107937
- 2026-10-09 Alias added: GHSA-7cpr-66jm-x98h
- 2026-10-10 Affected versions changed · Red Hat
- 2026-10-10 CVSS score added · Red Hat
- 2026-10-13 Affected versions changed · Red Hat
- 2026-10-16 CVSS score added · CISA ADP
- 2026-10-16 Weakness changed · CISA ADP
- 2026-10-16 CISA SSVC decision points changed
- 2026-10-16 Affected versions changed · Red Hat
- 2026-10-18 Priority changed: LOW → MEDIUM
- 2026-11-03 Affected versions changed · Red Hat
- 2026-11-06 Fix available: Red Hat Build of Apache Camel 3.33.4.SP3 · Red Hat
- 2026-11-06 Fix available: RHSA-2026:95622 · Red Hat
References
More Apache Cxf vulnerabilities
- TI-2019-09264 Incorrect authorization in Apache CXF CVSS 3.1CRITICAL 9.8
- TI-2020-10930 Apache CXF Reflected XSS in the services listing page via the styleSheetPath CVSS 3.1MEDIUM 6.1
- TI-2010-01990 Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in… CVSS 3.1CRITICAL 9.8
- TI-2022-22907 Apache CXF SSRF Vulnerability CVSS 3.1CRITICAL 9.8
- TI-2026-47481 Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage CVSS 3.1CRITICAL 9.8
- TI-2025-31053 Apache CXF: Untrusted JMS configuration can lead to RCE CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-107937 · CVE Program
- CVE-2026-107937 · NVD
- FIRST EPSS
- GHSA-7cpr-66jm-x98h · GitHub Advisory Database · CC BY 4.0
- CVE-2026-107937 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences