---
id: CVE-2026-107938
title: >-
  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
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 w…
severity: none
published: '2026-10-09'
updated: '2026-10-09'
sourceUpdated: '2026-10-09T16:33:39.007'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-107938'
references:
  - url: 'https://lists.apache.org/thread.html/ljsjsq1foyjy1v5o22oncw80twx7k2tc'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/10/09/13'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
ingestedAt: '2026-10-09T12:53:29.299Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
