Code execution via unvalidated JNDI transaction-manager lookup
Published Jun 12, 2026 · Updated Jun 12, 2026
JNDI injection in Apache CXF before 3.6.12, 4.0.0 through 4.1.6, and 4.2.0 through 4.2.1 allows attackers to execute code. JMSConfigFactory passes an endpoint-supplied transaction-manager JNDI name directly to InitialContext.lookup without validating the name. Exploitation requires control of Apache CXF JMS configuration and runs code with the privileges of the hosting Java process.
Summary
What happened
JNDI injection in Apache CXF before 3.6.12, 4.0.0 through 4.1.6, and 4.2.0 through 4.2.1 allows attackers to execute code. JMSConfigFactory passes an endpoint-supplied transaction-manager JNDI name directly to InitialContext.lookup without validating the name. Exploitation requires control of Apache CXF JMS configuration and runs code with the privileges of the hosting Java process.
The record
- CVE
- CVE-2026-50632
- Published
- Jun 12, 2026
- Updated
- Jun 12, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache CXF
- Classifications
- CWE-20, CWE-502
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 12, 2026CVE publishedPublication date reported by the CVE source.
- Jun 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.7
- Affected versionversion=4.2.0 <4.2.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo