Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.73% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-57819High confidence
Apache CXF: No default restriction on the amount of form parameters per message
Apache Software Foundation · Apache CXF
7.5HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 631 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Apache Software Foundation Apache CXF and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 631 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 631 affected or under-investigation product states without a fixed product state in the same current advisory
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-57819 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityApache CXF: Apache CXF: Denial of Service via uncontrolled form parameters
The vendor explicitly identifies these products as affected by this CVE.
- camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- Summary
- A flaw was found in Apache CXF. This vulnerability allows a remote attacker to initiate a Denial of Service (DoS) attack. The issue arises because the component does not enforce a default limit on the number of form parameters processed in a JAX-RS message, enabling an attacker to send requests with an excessive quantity of parameters, leading to resource exhaustion.
- Remediation
- Update Apache CXF to the latest version that includes the fix. Configure form parameter limits in application settings to prevent resource exhaustion attacks.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 631 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Apache CXF allows to set a limit on the number of form parameters in a JAX-RS message via the "maxFormParameterCount" configuration option. However, no default limit is set which may lead to denial of service attacks when processing requests with very large numbers of form parameters. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue by using a default limit of 500 parameters.
What
Apache CXF allows to set a limit on the number of form parameters in a JAX-RS message via the "maxFormParameterCount" configuration option. However, no default limit is set which may lead to denial of service attacks when processing requests with very large numbers of form parameters. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue by using a default limit of 500 parameters.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
Apache CXF allows to set a limit on the number of form parameters in a JAX-RS message via the "maxFormParameterCount" configuration option. However, no default limit is set which may lead to denial of service attacks when processing requests with very large numbers of form parameters. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue by using a default limit of 500 parameters.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Uncontrolled Resource Consumption → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-400 ↗
CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-frontend-jaxws as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-frontend-simple as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-management as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-rs-json-basic as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-rs-security-jose as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-security-saml as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-transports-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-ws-addr as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-ws-mex as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-ws-policy as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-ws-rm as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-ws-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-rt-wsdl as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-services-sts-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-tools-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-tools-java2ws as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- cxf-tools-validator as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- and 601 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- Update Apache CXF to the latest version that includes the fix. Configure form parameter limits in application settings to prevent resource exhaustion attacks.
04
Evidence and provenance
Published 6 Aug 2026 · Last source change 7 Aug 2026, 00:01 UTC · CWE-400 · Uncontrolled Resource Consumption
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-53852
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-jaxws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-simple as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-management as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-json-basic as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-security-jose as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security-saml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-transports-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-addr as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-mex as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-policy as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-rm as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-wsdl as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-services-sts-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-java2ws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-validator as a component of Red Hat build of Apache Camel 4 for Quarkus 3; and 682 more
- After
- camel-cxf-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-cxf-transport as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-cxf-soap-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-integration-tracing-opentelemetry as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-soap as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-bindings-xml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-databinding-jaxb as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-logging as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-features-metrics as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-jaxws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-frontend-simple as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-management as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-json-basic as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-rs-security-jose as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-security-saml as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-transports-http as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-addr as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-mex as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-policy as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-rm as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-ws-security as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-rt-wsdl as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-services-sts-core as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-common as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-java2ws as a component of Red Hat build of Apache Camel 4 for Quarkus 3; cxf-tools-validator as a component of Red Hat build of Apache Camel 4 for Quarkus 3; and 601 more
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.