Is CVE-2026-50633 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50633 being exploited in the wild.

How severe is CVE-2026-50633?

Critical severity, with a CVSS score of 9.8, published 12 June 2026.

Which products and versions are affected?

Apache Software Foundation CXF JCA integration module 4.2.0 to 4.2.1, all versions before 4.1.7; org.apache.cxf:cxf-integration-jca (Maven) ECOSYSTEM:introduced=4.2.0,fixed=4.2.2.

Is there a fix for CVE-2026-50633?

Yes. org.apache.cxf:cxf-integration-jca (Maven): upgrade to 4.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-50633 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-50633?

Check whether you run Apache Software Foundation CXF JCA integration module or org.apache.cxf:cxf-integration-jca (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50633: Apache CXF JNDI injection in JCA integration module

CVE-2026-50633 · Severity: critical · CVSS 9.8 · Published 2026-06-12

Apache CXF's JCA (Java Connector Architecture) integration module is vulnerable to JNDI injection attacks that allow remote code execution. An attacker who can manipulate the JCA deployment descriptor (ra.xml) or runtime activation parameters can inject malicious JNDI references and execute arbitrary code on the server. This affects integration points in messaging systems and application servers using CXF for JCA connectivity.

Vendors: Apache Software Foundation, Maven.

Quick answers

Is CVE-2026-50633 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50633 being exploited in the wild.
How severe is CVE-2026-50633?: Critical severity, with a CVSS score of 9.8, published 12 June 2026.
Which products and versions are affected?: Apache Software Foundation CXF JCA integration module 4.2.0 to 4.2.1, all versions before 4.1.7; org.apache.cxf:cxf-integration-jca (Maven) ECOSYSTEM:introduced=4.2.0,fixed=4.2.2.
Is there a fix for CVE-2026-50633?: Yes. org.apache.cxf:cxf-integration-jca (Maven): upgrade to 4.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50633 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50633?: Check whether you run Apache Software Foundation CXF JCA integration module or org.apache.cxf:cxf-integration-jca (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.cxf:cxf-integration-jca (Maven): upgrade to 4.2.2 or later

# set org.apache.cxf:cxf-integration-jca to 4.2.2 in your pom.xml or build.gradle

Technical details

This vulnerability is a JNDI injection flaw (CWE-502: Deserialization of Untrusted Data, CWE-20: Improper Input Validation) in Apache CXF's cxf-integration-jca module. The DispatchMDBMessageListenerImpl component fails to properly validate inputs when processing JCA activation parameters or the ra.xml deployment descriptor. An unauthenticated remote attacker with network access can exploit this by crafting malicious JNDI references that are resolved during deployment or activation, leading to arbitrary code execution with the privileges of the application server. The attack requires the ability to influence the ra.xml file or runtime activation parameters—typically available in JCA deployment scenarios. Fixes are available in versions 4.2.2 (for the 4.2.x branch) and 4.1.7 (for the 4.1.x and earlier branches).

Affected products

Apache CXF 4.2.0–4.2.1, 4.1.x before 4.1.7

Identifiers

CVE-2026-50633
GHSA-qp3f-rvj8-46c8

Timeline

2026-06-12: disclosed: Vulnerability publicly disclosed on GitHub Advisory Database and NVD
2026-06-12: patched: Patches released in versions 4.2.2 and 4.1.7

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.