Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-50632 — cxf-rt-transports-jms

HIGH

CVE-2026-50632 is a high-severity (CVSS 8.1) Improper Input Validation vulnerability in org.apache.cxf:cxf-rt-transports-jms. A fix is available for org.apache.cxf:cxf-rt-transports-jms — see the affected versions and patch details below.

Apache CXF: JNDI Injection Vulnerability in JMSConfigFactory

Also known asGHSA-93g8-qqv3-mrx8
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-50632.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-50632 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 382,621 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.apache.cxf:cxf-rt-transports-jms☕org.apache.cxf:cxf-rt-transports-jms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A further incomplete fix for a previous advisory CVE-2026-44417 (Untrusted JMS configuration can lead to RCE) for Apache CXF has been identified, which can allow code execution capabilities, if untrusted users are allowed to configure JMS for Apache CXF. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.cxf:cxf-rt-transports-jms≥ 4.2.0&&< 4.2.24.2.2org.apache.cxf:cxf-rt-transports-jms:4.2.2
☕Mavenorg.apache.cxf:cxf-rt-transports-jmsall versions4.1.7org.apache.cxf:cxf-rt-transports-jms:4.1.7

Affected Products

1 product · 2 configurations
Application
cxfapache
≥ 4.2.0 && < 4.2.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-transports-jms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.cxf:cxf-rt-transports-jms to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-50632 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This Important flaw in Apache CXF's JMS transport allows arbitrary code execution. The vulnerability occurs when untrusted users can configure Java Message Service (JMS) for Apache CXF, potentially leading to a complete system compromise. This risk is present in environments where JMS configuration is accessible to or…

Workaround published by Red Hat
To mitigate this issue, ensure that only trusted administrators have the necessary permissions to configure Java Message Service (JMS) for Apache CXF. Restricting access to JMS configuration prevents untrusted users from exploiting this vulnerability. Review and enforce strict access controls on systems where Apache CXF is deployed with JMS transport.
Source: Red Hat security advisory for CVE-2026-50632 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16cxf-rt-transports-jmsRHSA-2026:37390
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 10eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el10eapRHSA-2026:70230
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el8eapRHSA-2026:70228
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el9eapRHSA-2026:70229

Frequently Asked Questions

A further incomplete fix for a previous advisory CVE-2026-44417 (Untrusted JMS configuration can lead to RCE) for Apache CXF has been identified, which can allow code execution capabilities, if untrusted users are allowed to configure JMS for Apache CXF. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.
O3 Security · Impact-Aware SCA

Is CVE-2026-50632 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-50632: RCE — Fixed in 4.2.2 | O3 Security