Skip to main content
VulnerabilityPublished Updated

CVE-2026-71290: Apache HttpComponents Client · Improper Certificate Validation

Affects Apache HttpComponents ClientSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache HttpComponents ClientAffected
  • >=5.4-alpha <=5.6.3
Fixed in–
MavenApache Software Foundation/org.apache.httpcomponents.client5:httpclient5pkg:maven/Apache Software Foundation/org.apache.httpcomponents.client5:httpclient5Other threatsAffected
  • >=5.4-alpha <=5.6.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache HttpComponents Client to version 5.6.4 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated. Patch status is not explicitly stated but the vendor recommends upgrading to 5.6.4, which implies an official fix is available in that version.

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.

References

Community reviews

Loading reviews…