A JNDI Injection vulnerability has been discovered in Apache CXF's JCA integration module…
CVE-2026-50633 is a high-severity improper input validation vulnerability in Apache CXF from Apache, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.2.2, 4.1.7, 3.6.12 as the first without the flaw, so updating Apache CXF to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.92% chance of exploitation within 30 days, higher than 61% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache CXF to 4.2.2 or 4.1.7 or 3.6.12, whichever matches your release line, or a later version.
- Update Cxf to 3.6.12 or 4.1.7 or 4.2.2, whichever matches your release line, or a later version.
- Update Build Of Apache Camel to 4.18.1 or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache CXF | 4.2.0 up to, but not including, 4.2.2; 4.0.0 up to, but not including, 4.1.7; before 3.6.12 | 4.2.2, 4.1.7, 3.6.12 |
| Red Hat | Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16 | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | Not specified in the record | Not stated |
| Apache | Cxf | before 3.6.12; 4.0.0 up to, but not including, 4.1.7; 4.2.0 up to, but not including, 4.2.2 | 3.6.12, 4.1.7, 4.2.2 |
| Red Hat | Build Of Apache Camel | before 4.18.1; 4.18.1 | 4.18.1 |
| Red Hat | Fuse | 7.0.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CISA (ADP) |
| CVSS 3.1 | 8.1 | High | CNA |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- openwall.com/lists/oss-security/2026/06/11/10Mailing List, Third Party Advisory
- access.redhat.com/errata/RHSA-2026:37390Third Party Advisory
- access.redhat.com/security/cve/CVE-2026-50633Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2488307Issue Tracking, Third Party Advisory
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-50633.jsonThird Party Advisory
Other vulnerabilities in Apache CXF
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 9.1 Critical severity
Recent Improper Input Validation vulnerabilities
- 8.1 High severity
- 9.8 Critical severity
- 8.4 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.9 Critical severity
Spotted an error? Tell us.