Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Partial Red Hat: 1 without a fix
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and Red Hat.
Summary
In Apache CXF, the Netty-based HTTP client transport (cxf-rt-transports-http-netty-client) did not verify that the hostname in the server’s TLS certificate matched the host being called. This applied over both HTTP/1.1 and HTTP/2, even when disableCNCheck was left at its default value of false. The certificate chain was validated against the configured trust store, but the endpoint’s identity was not. A network attacker able to intercept traffic could present any certificate trusted by the client, such as a publicly issued certificate for a domain they control, and impersonate the target service. They could then read or modify the exchanged messages, including credentials. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Apache | Apache CXF | 4.2.0 to before 4.2.4; 4.0.0 to before 4.1.9; before 3.6.13 | 4.2.4, 4.1.9, 3.6.13 | Patch available | CNA |
- Apache CXF VendorApache Affected 4.2.0 to before 4.2.4; 4.0.0 to before 4.1.9; before 3.6.13 Fixed in 4.2.4, 4.1.9, 3.6.13 Patch available CNA
Remediation
- Fix · CNA Apache CXF (Apache Software Foundation) Fixed in 4.2.4, 4.1.9, 3.6.13
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache CXF 3.6.13, 4.1.9, 4.2.4
11 records Highest priority Priority MEDIUM 4 MEDIUM, 7 LOW
Other records, highest priority first
- TI-2026-69966 Authentication bypass in Apache CXF via weak STS token cache keysPriority MEDIUM 47
- TI-2026-69961 Apache CXF OIDC max_age check accepts sessions of any agePriority MEDIUM 47
- TI-2026-69969 Apache CXF header size limits bypass allows memory exhaustionPriority MEDIUM 40
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat build of Apache Camel for Spring Boot 4 | Affected | No fix yet |
Not affected: 1 product
- Red Hat Fuse 7
Timeline
- 2026-10-09 Threatist record created from CVE-2026-107938
- 2026-10-09 Alias added: GHSA-vr34-m3cj-mgxg
- 2026-10-16 CVSS score added · CISA ADP
- 2026-10-16 Weakness changed · CISA ADP
- 2026-10-16 CISA SSVC decision points changed
- 2026-10-16 Priority changed: LOW → MEDIUM
- 2026-10-30 Affected versions changed · Red Hat
- 2026-10-30 CVSS score added · Red Hat
- 2026-11-03 Affected versions changed · Red Hat
References
More Apache Cxf vulnerabilities
- TI-2019-09264 Incorrect authorization in Apache CXF CVSS 3.1CRITICAL 9.8
- TI-2020-10930 Apache CXF Reflected XSS in the services listing page via the styleSheetPath CVSS 3.1MEDIUM 6.1
- TI-2010-01990 Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in… CVSS 3.1CRITICAL 9.8
- TI-2022-22907 Apache CXF SSRF Vulnerability CVSS 3.1CRITICAL 9.8
- TI-2026-47481 Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage CVSS 3.1CRITICAL 9.8
- TI-2025-31053 Apache CXF: Untrusted JMS configuration can lead to RCE CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-107938 · CVE Program
- CVE-2026-107938 · NVD
- FIRST EPSS
- GHSA-vr34-m3cj-mgxg · GitHub Advisory Database · CC BY 4.0
- CVE-2026-107938 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences