CVE-2026-54225: Apache CXF: Denial of Service attack via large attachments
Apache CXF allows to control the maximum attachment size via the "attachment-max-size". Prior to Apache CXF 4.2.3 and 4.1.8 and 3.6.12, there was no default placed on this size, meaning that a denial of service attack is possible if the user doesn't explicitly set the limit. Users should update to Apache CXF 4.2.3 or 4.1.8 or 3.6.12 which fixes this problem by imposing a default attachment size limit of 50mb.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache CXFto a version that resolves this vulnerability.Fixed in 4.2.3 - Upgrade
Upgrade
Apache CXFto a version that resolves this vulnerability.Fixed in 4.1.8 - Upgrade
Upgrade
Apache CXFto a version that resolves this vulnerability.Fixed in 3.6.12
Event History
Frequently Asked Questions
What is the severity of CVE-2026-54225?
The severity of CVE-2026-54225 is classified as risk 29, indicating a significant potential impact.
What is CVE-2026-54225 about?
CVE-2026-54225 describes a vulnerability in Apache CXF where large attachments can lead to a denial of service attack if the attachment size limit is not configured.
How do I fix CVE-2026-54225?
To fix CVE-2026-54225, users should upgrade to Apache CXF versions 4.2.3, 4.1.8, or 3.6.12 or later, and configure the 'attachment-max-size' parameter.
Who is affected by CVE-2026-54225?
Users of Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected by CVE-2026-54225 due to the absence of a default attachment size limit.
What can happen if CVE-2026-54225 is not mitigated?
If CVE-2026-54225 is not mitigated, it can lead to a denial of service attack, potentially disrupting service availability.