VYPR
Unrated severityNVD Advisory· Published Jun 12, 2026· Updated Jun 12, 2026

CVE-2026-50645

CVE-2026-50645

Description

Apache CXF messages have no limit on attachment headers, enabling uncontrolled resource consumption and denial of service attacks.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Apache CXF messages have no limit on attachment headers, enabling uncontrolled resource consumption and denial of service attacks.

Vulnerability

Apache CXF versions 4.2.0 before 4.2.2 and all versions before 4.1.7 do not enforce any restriction on the number of attachment headers that a message can contain during deserialization. This allows an attacker to craft a message with a large number of attachment headers, leading to uncontrolled resource consumption. The affected component is the org.apache.cxf:cxf-core library [1].

Exploitation

An attacker can exploit this vulnerability by sending a specially crafted message to an Apache CXF endpoint that processes attachments. No authentication or prior access is required; the attacker only needs network access to the target service. The message contains an arbitrarily high number of attachment headers, which the deserialization process handles without any limit [1].

Impact

Successful exploitation causes uncontrolled resource consumption on the target server, which can lead to a denial of service (DoS) condition. The impact is primarily on resource availability, with no direct effect on confidentiality or integrity [1].

Mitigation

The vulnerability is fixed in Apache CXF versions 4.2.2 and 4.1.7, released June 11, 2026. These versions impose a default maximum of 500 attachments per message. Users should upgrade to the fixed versions. No workaround is mentioned in the available references [1].

AI Insight generated on Jun 12, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.