Description
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.
Published: 2026-08-06
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Apache CXF does not impose a default limit on the number of form parameters in a JAX-RS request, allowing an attacker to submit a request with a very large number of form fields. The lack of a limit can consume excessive memory and processing resources, leading to application slowdown or crash and thus a denial of service. The vulnerability is a classic resource exhaustion flaw as identified by CWE-400.

Affected Systems

All Apache CXF releases prior to versions 4.2.3, 4.1.8, and 3.6.12 are affected. These versions lack the default 500‑parameter cap introduced in the later releases. Users running older or unpatched CXF deployments should review their version and apply the recommended upgrade if possible.

Risk and Exploitability

The vulnerability can be triggered by sending an HTTP request containing a large number of form parameters; no authentication or privileged state is required. The CVSS score of 7.5 signifies a high severity, indicating significant potential impact to availability. Though no EPSS value is available, the absence of a default limit indicates a feasible exploitation path, especially against publicly exposed APIs. Since the issue is not listed in CISA KEV, it has not yet been identified as a widely exploited vulnerability, but the potential for denial of service remains significant for exposed services.

Generated by OpenCVE AI on August 6, 2026 at 17:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to 4.2.3 or newer, or 4.1.8 or 3.6.12 where a 500‑parameter default limit is enforced
  • If an upgrade is not immediately possible, configure the maxFormParameterCount setting to a conservative value that matches your business requirements
  • Implement input size limits at the reverse‑proxy or network edge to reject requests exceeding a safe payload size before they reach CXF

Generated by OpenCVE AI on August 6, 2026 at 17:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 06 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 06 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache cxf
Vendors & Products Apache
Apache cxf

Thu, 06 Aug 2026 11:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache CXF: No default restriction on the amount of form parameters per message
Weaknesses CWE-400
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-08-07T00:01:43.594Z

Reserved: 2026-06-25T10:54:03.855Z

Link: CVE-2026-57819

cve-icon Vulnrichment

Updated: 2026-08-07T00:01:43.594Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-06T17:30:16Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption