CVE-2026-66909

Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage

Published Aug 6, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.

Analysis

AI-generated

Technical impact

Apache CXF’s JMS transport naïvely deserializes the body of any inbound JMS ObjectMessage using native Java deserialization without type checks. This flaw allows an attacker who can place a message on the service’s JMS destination to inject a malicious serialized object. Depending on the classpath contents, the payload can either trigger a denial‑of‑service or execute arbitrary code on the host. The presence of suitable gadget classes is a prerequisite for remote code execution but even without them a non‑replicated attacker can still crash the service by corrupting its state.

Affected Systems

The issue affects installations of Apache CXF that rely on the JMS transport. The Apache Software Foundation has released mitigations in version 4.2.3, 4.1.8 and 3.6.12, which disable ObjectMessage deserialization by default and provide a configuration option to re‑enable it if required.

Risk and Exploitability

The EPSS score for this vulnerability is not available, and it is not listed in the CISA KEV catalog, so publicly documented exploitation data is missing. However, the opportunity to deliver a serialized payload via JMS is accessible when an application publishes or consumes messages, making the attack vector plausible in many deployments. The CVSS score is 9.8, indicating a critical severity for remote code execution. Administrators should treat the vulnerability with urgency until a patch is available or a mitigation is applied.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to version 4.2.3, 4.1.8 or 3.6.12 to apply the vendor fix that disables ObjectMessage deserialization by default.
  • If an upgrade is not immediately possible, reconfigure the JMS transport to disable ObjectMessage deserialization through the provided configuration switch.
  • Ensure that any unused or potentially dangerous gadget classes are removed from the application’s classpath and validate that the application does not accept JMS ObjectMessages from untrusted sources.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache
Apache cxf
Vendors & Products Apache
Apache cxf
Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

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

Type Values Removed Values Added
Description Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place. Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.
Title Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage
Weaknesses CWE-502
References
Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 7, 2026, 12:01 AM
Reserved
Jul 28, 2026, 9:44 AM
Status
Modified
Published
Aug 6, 2026, 11:16 AM
Modified
Oct 24, 2026, 4:10 PM
Severity
Important
Public date
Aug 6, 2026, 10:23 AM