dbcve.org
CxfApplication · Apache

CVE-2026-50645

HIGH · 7.5 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 4.1.7 / 4.2.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 or 3.6.12, which fix this issue by imposing a maximum default of 500 attachments per message.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache CXF fails to impose limits on attachment headers during message deserialization, allowing an attacker to send messages with unlimited attachments and exhaust server resources leading to denial of service.

MitigationUpgrade Apache CXF to version 4.2.2 or 4.1.7 which enforces a maximum of 500 attachments per message by default.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CxfApplication
Affected:< 4.1.7>= 4.2.0, < 4.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache CXF version
    Locate the CXF jar files in your application (typically in WEB-INF/lib or classpath) and check the version from filenames like cxf-core-*.jar, cxf-*.jar, or run: grep -r "cxf" pom.xml if using Maven, or check your dependency management system
    Affected if The installed version is less than 4.1.7, or greater than or equal to 4.2.0 but less than 4.2.2
  2. Determine if attachment processing is enabled
    Check your CXF service configuration files (beans.xml, cxf.xml, or Spring Boot auto-configuration) for elements like <attachment>, <jaxws:endpoint>, or MTOM-enabled service definitions. Also inspect code for AttachmentSerializer/AttachmentDeserializer usage
    Affected if CXF is configured to process SOAP or MTOM attachments, as this is the code path that performs deserialization without limits
  3. Check for custom attachment limits
    Search configuration files and code for properties like "attachment-max-count", "attachment-max-size", or custom AttachmentDeserializer implementations that might impose limits
    Affected if No custom attachment limit is configured and the CXF version falls within the affected range, the default unlimited behavior applies

You are affected if your CXF version is vulnerable (less than 4.1.7 or between 4.2.0 and 4.2.2) AND your application processes inbound attachments without custom limits configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.7 / 4.2.2 or later
Fixed in 4.1.74.2.2
Interim mitigation

Upgrade Apache CXF to version 4.2.2 or 4.1.7 which enforces a maximum of 500 attachments per message by default.

Recommended fix High confidence

CXF 4.2.2 or CXF 4.1.7 (select based on current version branch)

  1. 1. Identify the current Apache CXF version in use by checking project dependencies (Maven pom.xml, Gradle build file, or application libraries)
  2. 2. Determine the appropriate upgrade path based on current version: if using 4.1.x series, upgrade to 4.1.7; if using 4.2.0 or 4.2.1, upgrade to 4.2.2
  3. 3. Update the dependency configuration: for Maven, change the CXF version in pom.xml to either 4.1.7 or 4.2.2; for Gradle, update the CXF dependency version
  4. 4. Rebuild the application with the new dependency version
  5. 5. Run existing tests to verify compatibility with the new CXF version
  6. 6. Verify that the fix is active by confirming the default maximum of 500 attachments per message is enforced
Caveat Minor risk: upgrading within same major.minor version should be low-risk; however, always review release notes for any breaking changes between the current version and 4.1.7/4.2.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cxf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50645 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data