cve.bz

CVE-2026-107937 apache cxf

7.5 highEPSS 0.6%

High (7.5) in apache cxf. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-107937 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107937?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107937?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107937 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-107937

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-107937](https://cve.bz/cve/badge/CVE-2026-107937.svg)](https://cve.bz/cve/CVE-2026-107937)

HTML:

<a href="https://cve.bz/cve/CVE-2026-107937"><img src="https://cve.bz/cve/badge/CVE-2026-107937.svg" alt="CVE-2026-107937"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.4
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.9
Apache Software Foundation Apache CXFbefore 3.6.13

Red Hat

Red Hat rates this Important.

Red Hat's statement

An Important severity denial of service flaw was found in Apache CXF, which is shipped in Red Hat JBoss Fuse 7, Red Hat JBoss Enterprise Application Platform 7 and 8, Red Hat Single Sign-On 7, Red Hat JBoss Web Server 5, and Red Hat build of Apache Camel. The parser for multipart/MTOM attachment part headers did not fully enforce the configured attachment-max-header-size and attachment-headers-max-count limits: the size limit was applied only to each physical line rather than to a header value built from continuation lines or to the combined values of a repeated header, and the count limit was checked against the number of distinct header names rather than the total number of header lines. A remote, unauthenticated attacker could send a crafted multipart request with very large folded or repeated part headers, causing the server to allocate memory without bound and resulting in a denial of service. Red Hat JBoss EAP XP 6 is not affected because the vulnerable cxf-core component is not present in that configuration. Fixes for the in-support affected products are being pursued by the responsible engineering teams; the EAP 7.4 and JBoss Web Server 5 streams are outside active support scope, and Red Hat Single Sign-On 7 will not receive a fix for this issue.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3cxf-coreAffected
Red Hat build of Apache Camel for Spring Boot 4cxf-coreAffected
Red Hat Fuse 7cxf-coreNot affected
Red Hat JBoss Enterprise Application Platform 7cxf-coreOut of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 8cxf-coreAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcxf-coreNot affected
Red Hat JBoss Web Server 5cxf-coreOut of support scope
Red Hat Single Sign-On 7cxf-coreWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107937.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON