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

Impact

Apache CXF allows administrators to control the maximum size of attachments through the "attachment-max-size" setting. Prior to versions 4.2.3, 4.1.8, and 3.6.12, no default size limit was enforced. This omission permits an attacker to send exceedingly large attachments, overwhelming system resources and causing the service to become unavailable. The vulnerability falls under CWE‑770, indicating that it arises from unchecked resource consumption.

Affected Systems

The affected product is Apache CXF, maintained by the Apache Software Foundation. Versions before 4.2.3, 4.1.8, and 3.6.12 are impacted. Users should verify that they are not running any of these legacy releases.

Risk and Exploitability

While an official EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, the lack of a size constraint introduces a high likelihood of successful denial‑of‑service exploitation, especially when an attacker can submit large payloads to the service. The attack vector is inferred to be remote, given that the vulnerability is triggered by external attachment submissions. The damage profile is high, as resource exhaustion can render the impacted service—and potentially dependent systems—unresponsive until remedial action is taken.

Generated by OpenCVE AI on August 6, 2026 at 12:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to version 4.2.3, 4.1.8, or 3.6.12 to enforce the 50 MB default attachment size limit.
  • If an upgrade is not immediately possible, configure the "attachment-max-size" property with a safe cap (e.g., 50 MB) to prevent oversized attachments from consuming resources.
  • Monitor memory and resource usage on servers running Apache CXF, and consider implementing additional rate‑limiting controls on incoming attachment traffic.

Generated by OpenCVE AI on August 6, 2026 at 12:22 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 11:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache CXF: Denial of Service attack via large attachments
Weaknesses CWE-770
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-08-06T15:11:59.864Z

Reserved: 2026-06-12T12:43:10.607Z

Link: CVE-2026-54225

cve-icon Vulnrichment

Updated: 2026-08-06T15:11:57.079Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-06T12:30:03Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling