CVE-2026-50645GHSA-GHVC-7HP8-2G2V
Apache CXF: No restriction on attachment headers per message
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Fix
- Fixed in 4.2.2, 4.1.7, 3.6.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
There is no restriction on the amount of attachment headers that a message can contain when being deserialized by Apache CXF, which can lead to uncontrolled resource consumption or a denial of service attack. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fix this issue by imposing a maximum default of 500 attachments per message.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- org.apache.cxf:cxf-core
From 4.2.0 · fixed in 4.2.2; From 4.0.0 · fixed in 4.1.7; fixed in 3.6.12
- org.apache.cxf:cxf-coreMaven
From 4.2.0 · fixed in 4.2.2
- org.apache.cxf:cxf-coreMaven
From 4.0.0 · fixed in 4.1.7
- org.apache.cxf:cxf-coreMaven
fixed in 3.6.12