How severe is CVE-2026-66909?

CVE-2026-66909 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-66909 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-66909?

CVE-2026-66909 affects Apache Cxf. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-66909?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-66909 published?

CVE-2026-66909 was published on 2026-08-06 and last updated on 2026-08-07.

CVE-2026-66909

CVE-2026-66909 is a critical-severity vulnerability in Apache Cxf with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-502.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-502
Affected product: Apache Cxf
Published: 2026-08-06
Last modified: 2026-08-07

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.

Frequently asked questions

What is CVE-2026-66909?: 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.
How severe is CVE-2026-66909?: CVE-2026-66909 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-66909 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-66909?: CVE-2026-66909 affects Apache Cxf. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-66909?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-66909 published?: CVE-2026-66909 was published on 2026-08-06 and last updated on 2026-08-07.

References

Affected products (1)

cpe:2.3:a:apache:cxf:*:*:*:*:*:*:*:*

More vulnerabilities in Apache Cxf

CVE-2012-2379 — Critical (CVSS 10.0): Apache CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child…
CVE-2026-68079 — Critical (CVSS 9.8): In Apache CXF's DefaultEncryptingCodeDataProvider, a captured authorization code can be redeemed an unlimited number…
CVE-2026-50628 — Critical (CVSS 9.8): A logic error in OAuthRequestFilter rejects legitimate requests originating from the bound IP address, while blindly…
CVE-2026-49875 — Critical (CVSS 9.8): Apache CXF's EndpointReferenceUtils and W3CMultiSchemaFactory classes construct a SAXParserFactory without the…
CVE-2026-44930 — Critical (CVSS 9.8): An LDAP injection vulnerability in the LDAP Certificate repository of the XKMS server in Apache CXF may allow an…
CVE-2025-48913 — Critical (CVSS 9.8): If untrusted users are allowed to configure JMS for Apache CXF, previously they could use RMI or LDAP URLs, potentially…

All CVEs affecting Apache Cxf →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

CVE-2026-69836 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Entra ID allows an unauthorized attacker to execute code over a network.
CVE-2026-17061 — Critical (CVSS 10.0): A Deserialization of Untrusted Data vulnerability affecting SIMULIA Execution Engine from Release 2023 through Release…
CVE-2026-11756 — Critical (CVSS 10.0): A Deserialization of Untrusted Data vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release…
CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →