CVE-2026-107938

Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.

Published Oct 9, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Apache CXF’s Netty-based HTTP client transport does not verify that the hostname in a server’s TLS certificate matches the target host, even when the disableCNCheck flag remains at its default false value. This omission lets an attacker who can intercept or observe the client‑server communication present any certificate that the client trusts, regardless of the domain for which it was issued. The attacker can then impersonate the intended service, read the encrypted payload, or modify messages—including credentials—during transit.

Affected Systems

Apache Software Foundation’s Apache CXF, specifically its Netty HTTP client transport (cxf-rt-transports-http-netty-client). All releases older than 4.2.4, 4.1.9, or 3.6.13 are vulnerable to this hostname‑verification deficiency.

Risk and Exploitability

EPSS information is not available and the vulnerability has not been cataloged in CISA KEV. The attack requires the attacker to control or observe the network path between client and server, which is an inference from the described interception scenario. If achieved, the attacker gains the ability to substitute any trusted certificate issued for a different domain and thus performs a man‑in‑the‑middle attack, fully compromising confidentiality and integrity of the TLS protected traffic. The CVSS score for this vulnerability is not available.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache CXF to the latest fixed releases—4.2.4, 4.1.9, or 3.6.13—to enable hostname verification in the Netty client transport.
  • Validate the trusted certificate store to ensure it contains only certificates necessary for the application’s intended communications, removing any unnecessary trusted certificates for unrelated domains.
  • As a proactive best practice, keep the Netty client library and any associated dependencies updated to their most recent secure versions and monitor TLS handshakes for mismatched hostnames or certificate validation failures that could indicate an attempted man‑in‑the‑middle attack.

Generated by OpenCVE AI on October 9, 2026 at 12:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:cxf:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-297
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache cxf
Vendors & Products Apache
Apache cxf
Type Values Removed Values Added
Weaknesses CWE-295
Type Values Removed Values Added
Description 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.
Title Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.
References
Weaknesses
  • CWE-295

    Improper Certificate Validation

  • CWE-297

    Improper Validation of Certificate with Host Mismatch

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Oct 15, 2026, 5:49 PM
Reserved
Oct 9, 2026, 9:19 AM
Status
Analyzed
Published
Oct 9, 2026, 11:17 AM
Modified
Oct 16, 2026, 6:11 PM