Apache CXF up to 3.6.11/4.1.7/4.2.2 attachment-max-size resource consumption

Summaryinfo

A vulnerability was found in Apache CXF up to 3.6.11/4.1.7/4.2.2. It has been rated as problematic. The impacted element is an unknown function. Performing a manipulation of the argument attachment-max-size results in resource consumption. This vulnerability is reported as CVE-2026-54225. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Apache CXF up to 3.6.11/4.1.7/4.2.2. It has been classified as problematic. This affects an unknown function. The manipulation of the argument attachment-max-size with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:

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.

It is possible to read the advisory at lists.apache.org. This vulnerability is uniquely identified as CVE-2026-54225 since 06/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/06/2026). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 3.6.12, 4.1.8 or 4.2.3 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Application Server Software

Vendor

• Apache

Name

• CXF

Version

• 3.6.0
• 3.6.1
• 3.6.2
• 3.6.3
• 3.6.4
• 3.6.5
• 3.6.6
• 3.6.7
• 3.6.8
• 3.6.9
• 3.6.10
• 3.6.11
• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3
• 4.1.4
• 4.1.5
• 4.1.6
• 4.1.7
• 4.2.0
• 4.2.1
• 4.2.2

License

• open-source

Website

• Vendor: https://www.apache.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion