CVE-2026-57819: Apache CXF · Uncontrolled Resource Consumption
Affects Apache CXFSource CVE Database V5
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
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache CXF | Affected
| Fixed in
|
| Apache Software FoundationApache CXF | Affected
| Fixed in
|
| Apache Software FoundationApache CXF | Affected
| Fixed in
|
MavenApache Software Foundation/org.apache.cxf:cxf-rt-frontend-jaxrspkg:maven/Apache Software Foundation/org.apache.cxf:cxf-rt-frontend-jaxrsOther threats | Affected
| Fixed in
|
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 Apache CXF to version 4.2.3, 4.1.8, or 3.6.12 or later, where a default limit of 500 form parameters is enforced. This official fix mitigates the risk of denial of service due to uncontrolled resource consumption. No other mitigation is indicated by the vendor advisory.
Description
Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 do not set a default limit on the number of form parameters in JAX-RS messages. This lack of a default limit can lead to uncontrolled resource consumption, potentially causing denial of service (DoS) conditions when processing requests with very large numbers of form parameters. The issue is addressed by introducing a default limit of 500 parameters in the fixed versions.