WaratekVRT Sign in
Reset
More filters (2)
Columns
Including CVEs outside Waratek scope✕Vendor apache✕Product httpclient✕
Overview 11 matches · 10 in Waratek scope · 3 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
11matches 10in Waratek scope90.9% 3protected27.3% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 3 27.3% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 7 63.6% Outside Waratek scope 1 9.1% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 2 18.2% High 2 18.2% Medium 7 63.6% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 3 27.3% partly blocked 0 0.0% not blocked 8 72.7% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 11 100.0%
split by peak 3 / year
Outside Waratek scope: 1No exploit published: 7Protected by Waratek: 3 Medium: 7High: 2Critical: 2 not blocked: 8blocked by ARMR today: 3 No public exploit: 11
20111 No exploit published1 Medium1 not blocked1 No public exploit1 20121 Protected by Waratek1 Medium1 blocked by ARMR today1 No public exploit1 20130 20142 Protected by Waratek2 Medium2 blocked by ARMR today2 No public exploit2 20151 No exploit published1 Medium1 not blocked1 No public exploit1 20160 20171 No exploit published1 Critical1 not blocked1 No public exploit1 20180 20190 20201 Outside Waratek scope1 Medium1 not blocked1 No public exploit1 20210 20220 20230 20240 20251 No exploit published1 High1 not blocked1 No public exploit1 20263 No exploit published3 Critical1 High1 Medium1 not blocked3 No public exploit3
20122014201620182020202220242026
11 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2026-71290 Critical 2026-08-11 No exploit published No public exploit 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.
CVE-2026-64607 Medium 2026-07-31 No exploit published No public exploit HttpClient based on the classic i/o model fails to correctly release the underlying connection back to the connection manager if it encounters an invalid or unsupported `Content-Encoding` header value in the response message. Please note this defect does not affect HttpClient based on the async i/o model. This issue affects Apache HttpComponents Client: from 5.0-alpha1 through 5.6.2.
CVE-2026-40542 High 2026-04-22 No exploit published No public exploit Missing critical step in authentication in Apache HttpClient 5.6 allows an attacker to cause the client to accept SCRAM-SHA-256 authentication without proper mutual authentication verification. Users are recommended to upgrade to version 5.6.1, which fixes this issue.
CVE-2025-27820 High 2025-04-24 No exploit published No public exploit A bug in PSL validation logic in Apache HttpClient 5.4.x disables domain checks, affecting cookie management and host name verification. Discovered by the Apache HttpClient team. Fixed in the 5.4.3 release
CVE-2020-13956 Medium 2020-12-02 Outside Waratek scope No public exploit Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution.
CVE-2013-4366 Critical 2017-10-30 No exploit published No public exploit http/impl/client/HttpClientBuilder.java in Apache HttpClient 4.3.x before 4.3.1 does not ensure that X509HostnameVerifier is not null, which allows attackers to have unspecified impact via vectors involving hostname verification.
CVE-2015-5262 Medium 2015-10-27 No exploit published No public exploit http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting during an SSL handshake, which allows remote attackers to cause a denial of service (HTTPS call hang) via unspecified vectors.
CVE-2012-6153 Medium 2014-09-04 Protected by Waratek No public exploit http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before 4.2.3 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5783.
CVE-2014-3577 Medium 2014-08-21 Protected by Waratek No public exploit org.apache.http.conn.ssl.AbstractVerifier in Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a "CN=" string in a field in the distinguished name (DN) of a certificate, as demonstrated by the "foo,CN=www.apache.org" string in the O field.
CVE-2012-5783 Medium 2012-11-04 Protected by Waratek No public exploit Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
CVE-2011-1498 Medium 2011-07-07 No exploit published No public exploit Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with an authenticating proxy server, sends the Proxy-Authorization header to the origin server, which allows remote web servers to obtain sensitive information by logging this header.