CVE-2026-66909
Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage
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.
INFO
Published Date :
Aug. 6, 2026, 11:16 a.m.
Last Modified :
Aug. 6, 2026, 11:16 a.m.
Remotely Exploit :
No
Source :
[email protected]
Solution
- Upgrade to Apache CXF version 4.2.3 or later.
- Upgrade to Apache CXF version 4.1.8 or later.
- Upgrade to Apache CXF version 3.6.12 or later.
- Disable ObjectMessage deserialization if upgrading is not possible.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-66909.
| URL | Resource |
|---|---|
| https://lists.apache.org/thread/lr5d4tg6tf7j29jmw8wt242oowonjqpx |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-66909 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-66909
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-66909 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-66909 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Aug. 06, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'Apache Software Foundation', 'product': 'Apache CXF', 'versions': [{'status': 'affected', 'version': '4.2.0', 'lessThan': '4.2.3', 'versionType': 'semver'}, {'status': 'affected', 'version': '4.0.0', 'lessThan': '4.1.8', 'versionType': 'semver'}, {'status': 'affected', 'version': '0', 'lessThan': '3.6.12', 'versionType': 'semver'}], 'packageName': 'org.apache.cxf:cxf-rt-transports-jms', 'collectionURL': 'https://repo.maven.apache.org/maven2', 'defaultStatus': 'unaffected'}] 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. Added CWE CWE-502 Added Reference https://lists.apache.org/thread/lr5d4tg6tf7j29jmw8wt242oowonjqpx