CVE-2026-50633 — cxf-integration-jca
HIGHCVE-2026-50633 is a high-severity (CVSS 8.1) Improper Input Validation vulnerability in org.apache.cxf:cxf-integration-jca. A fix is available for org.apache.cxf:cxf-integration-jca — see the affected versions and patch details below.
Apache CXF: JNDI Injection vulnerability in DispatchMDBMessageListenerImpl
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-50633.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-50633 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
org.apache.cxf:cxf-integration-jca☕org.apache.cxf:cxf-integration-jcaReal-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 JNDI Injection vulnerability has been discovered in Apache CXF's JCA integration module, which can allow for code execution, if an attacker is able to manipulate the JCA deployment descriptor (ra.xml) or runtime activation parameters. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.cxf:cxf-integration-jca | ≥ 4.2.0&&< 4.2.2 | 4.2.2org.apache.cxf:cxf-integration-jca:4.2.2 |
| ☕Maven | org.apache.cxf:cxf-integration-jca | all versions | 4.1.7org.apache.cxf:cxf-integration-jca:4.1.7 |
Affected Products
cxfapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-integration-jca, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:cxf-integration-jca to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-50633 is resolved across your whole dependency graph.
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.
This is an Important vulnerability in Apache CXF's JCA integration module, as shipped in Red Hat products such as JBoss Fuse and Red Hat build of Apache Camel. This JNDI Injection flaw could lead to arbitrary code execution if an attacker successfully manipulates the JCA deployment descriptor or runtime activation…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2026-50633 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16 | cxf-integration-jca | RHSA-2026:37390 |
Frequently Asked Questions
Is CVE-2026-50633 in your dependencies?
Find it across Maven, including transitive dependencies.