There is no restriction on the amount of attachment headers that a message can contain when being deserialized by Apache CXF, which can lead to uncontrolled resource consumption or a denial of service attack. Users are recommended to upgrade to versions 4.2.2 or 4.1.7, which fix this issue by imposing a maximum default of 500 attachments per message.
Metrics
Affected Vendors & Products
References
History
Fri, 12 Jun 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache cxf |
|
| Vendors & Products |
Apache
Apache cxf |
Fri, 12 Jun 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 12 Jun 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | There is no restriction on the amount of attachment headers that a message can contain when being deserialized by Apache CXF, which can lead to uncontrolled resource consumption or a denial of service attack. Users are recommended to upgrade to versions 4.2.2 or 4.1.7, which fix this issue by imposing a maximum default of 500 attachments per message. | |
| Title | Apache CXF: No restriction on attachment headers per message | |
| Weaknesses | CWE-400 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-06-12T09:28:15.759Z
Reserved: 2026-06-05T14:05:01.499Z
Link: CVE-2026-50645
No data.
Status : Received
Published: 2026-06-12T10:16:23.533
Modified: 2026-06-12T10:16:23.533
Link: CVE-2026-50645
No data.
OpenCVE Enrichment
Updated: 2026-06-12T10:30:24Z