Skip to main content
VulnerabilityPublished

CVE-2026-54225: Apache CXF · Unthrottled Resource Allocation

Affects Apache CXFSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 4.2.3 : patch Apache CXF soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.2.3, 4.1.8, 3.6.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Apache to 4.2.3, 4.1.8 or 3.6.12.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache CXFAffected
  • >=4.2.0 <4.2.3
Fixed in
  • 4.2.3
Apache Software FoundationApache CXFAffected
  • >=4.0.0 <4.1.8
Fixed in
  • 4.1.8
Apache Software FoundationApache CXFAffected
  • <3.6.12
Fixed in
  • 3.6.12
MavenApache Software Foundation/org.apache.cxf:cxf-corepkg:maven/Apache Software Foundation/org.apache.cxf:cxf-coreOther threatsAffected
  • >=4.2.0 <4.2.3
  • >=4.0.0 <4.1.8
  • <3.6.12
Fixed in
  • 4.2.3
  • 4.1.8
  • 3.6.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache CXF versions 4.2.3, 4.1.8, or 3.6.12 or later, which implement a default maximum attachment size limit of 50MB. Until upgraded, users should manually configure the "attachment-max-size" property to limit attachment sizes and prevent resource exhaustion. Patch status is not explicitly stated but the fixed versions are identified, so upgrading to these versions is the recommended remediation.

Description

Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 do not impose a default limit on the maximum attachment size, which can lead to denial of service (DoS) attacks if users do not explicitly configure this limit. The issue is addressed by setting a default attachment size limit of 50MB in the fixed versions.

References

Community reviews

Loading reviews…