CVE-2026-66909 json
Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage
published 2026-08-06 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-53854
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Apache Software Foundation Apache CXF 3.6.12, 4.1.8, 4.2.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-66909 updated cvss 8.1
org.apache.cxf/cxf: Apache CXF: Remote Code Execution via unsafe deserialization of JMS ObjectMessage
-
Red Hat JBoss Enterprise Application Platform 7 cxf-rt-transports-jms, cxf 3.3.9.redhat-00001, eap74-els-openjdk8-openshift-rhel8, eap74-els-openjdk11-openshift-rhel8, eap74-els-openjdk17-openshift-rhel8, jboss-eap-7-eap74-els-openjdk8-openshift-rhel8, +1 moreaffected: workaround, no fix available, no fix planned “Will not fix”
-
Red Hat Single Sign-On 7 cxf-rt-transports-jmsaffected: workaround, no fix planned “Out of support scope”
-
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16fixed: vendor fix RHSA-2026:71675
-
Red Hat JBoss Enterprise Application Platform 8.1fixed: vendor fix RHSA-2026:95887
-
Red Hat JBoss Enterprise Application Platform Expansion Pack cxf-rt-transports-jmsnot affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3 mo ago
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Apache Software Foundation Apache CXF
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
lists.apache.org
/thread/lr5d4tg6tf7j29jmw8wt242oowonjqpx
vendor-advisory, mailing-list
- openwall.com /lists/oss-security/2026/08/06/18
Sources
- CVE List CVE-2026-66909
- NVD CVE-2026-66909
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.