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.
References
| Link | Resource |
|---|---|
| https://lists.apache.org/thread/lr5d4tg6tf7j29jmw8wt242oowonjqpx | Mailing List Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2026/08/06/18 |
Configurations
Configuration 1 (hide)
|
History
23 Oct 2026, 21:10
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
Information
Published : 2026-08-06 11:16
Updated : 2026-10-24 16:10
NVD link : CVE-2026-66909
Mitre link : CVE-2026-66909
CVE.ORG link : CVE-2026-66909
JSON object : View
Products Affected
apache
- cxf
CWE
CWE-502
Deserialization of Untrusted Data
