CVE-2026-71290

Apache HttpComponents Client: TLS hostname verification silently disabled on the async transport (default config, MITM)

Published Aug 11, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain. 


Please note the classic version of HttpClient is not affected by this vulnerability. 

Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.

Analysis

AI-generated

Technical impact

The updated CVE description indicates that an attacker who can intercept traffic between the Apache HttpComponents Client and a server can bypass TLS hostname verification in the async transport by presenting a valid certificate for a different domain. This flaw removes the core assurance of TLS that the presented certificate corresponds to the intended host, allowing a MITM to impersonate the server and read or modify traffic without detection.

Affected Systems

Apache HttpComponents Client 5.4 through 5.6.3 is affected. The classic (non‑async) HttpClient is not impacted. Users running any of the vulnerable async clients should upgrade to at least version 5.6.4, which contains the fix.

Risk and Exploitability

An active network attacker who can intercept traffic between the client and server can exploit this flaw. Although the EPSS score is below 1%, indicating current exploitation probability is low, the impact of a successful attack is severe because TLS assurance is compromised. The vulnerability is not listed in the CISA KEV catalog, but organizations using the vulnerable client should aim to remediate quickly as the attack vector—MITM—is straightforward and requires only control over network traffic or DNS manipulation. The CVSS score of 9.1 indicates high severity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache HttpComponents Client to version 5.6.4 or later to resolve the hostname verification bypass.
  • Review application code to ensure the async transport uses the HostnameVerificationPolicy#BUILTIN setting; if upgrade is delayed, consider migrating to the classic HttpClient or disabling async usage until the patch is applied.
  • Deploy network‑level monitoring or TLS inspection to flag unexpected certificate changes, helping detect MITM attempts while remediation is in progress.

Generated by OpenCVE AI on August 13, 2026 at 10:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache httpclient
CPEs cpe:2.3:a:apache:httpclient:*:*:*:*:*:*:*:*
Vendors & Products Apache httpclient
Type Values Removed Values Added
Description Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue. Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.
Type Values Removed Values Added
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 httpcomponents Client
Vendors & Products Apache
Apache httpcomponents Client
Type Values Removed Values Added
Description Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.
Title Apache HttpComponents Client: TLS hostname verification silently disabled on the async transport (default config, MITM)
Weaknesses CWE-295
References
Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 24, 2026, 3:55 AM
Reserved
Aug 5, 2026, 12:30 PM
Status
Analyzed
Published
Aug 11, 2026, 9:17 PM
Modified
Oct 24, 2026, 3:10 PM
Severity
Important
Public date
Aug 11, 2026, 8:33 PM