VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.httpcomponents.client5:httpclient5: vulnerability history, versions and safety

org.apache.httpcomponents.client5:httpclient5 is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 46 releases, from Apr 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 31 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.httpcomponents.client5:httpclient5 vulnerabilities

Vulert verdict on org.apache.httpcomponents.client5:httpclient5 5.7-beta1 i

Updated on 23 Oct 2026

Good news: 5.7-beta1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 5.7-beta1 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.7-beta1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.7-beta1 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 2 in the last year i
  • Latest disclosure 31 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.httpcomponents.client5:httpclient5, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.7-beta1 19 Oct 2026 none Apache-2.0 — Details →
5.6.5 06 Oct 2026 none Apache-2.0 — Details →
5.7-alpha1 07 Aug 2026 none Apache-2.0 — Details →
5.6.4 06 Aug 2026 none Apache-2.0 — Details →
5.6.3 27 Jul 2026 none Apache-2.0 — Details →
5.6.2 26 Jun 2026 M1 Apache-2.0 Yes Details →
5.6.1 15 Apr 2026 M1 Apache-2.0 Yes Details →
5.6 17 Dec 2025 H1 M1 Apache-2.0 Yes Details →
5.5.2 16 Dec 2025 M1 Apache-2.0 Yes Details →
5.6-alpha1 21 Oct 2025 H1 M1 Apache-2.0 Yes Details →
5.5.1 23 Sep 2025 M1 Apache-2.0 Yes Details →
5.5 18 May 2025 M1 Apache-2.0 Yes Details →
5.4.4 21 Apr 2025 M1 Apache-2.0 Yes Details →
5.4.3 23 Mar 2025 M1 Apache-2.0 Yes Details →
5.5-alpha1 10 Feb 2025 M1 Apache-2.0 Yes Details →
5.4.2 28 Jan 2025 H1 M1 Apache-2.0 Yes Details →
5.4.1 25 Oct 2024 H1 M1 Apache-2.0 Yes Details →
5.4 16 Sep 2024 H1 M1 Apache-2.0 Yes Details →
5.4-beta1 23 Jun 2024 H1 M1 Apache-2.0 Yes Details →
5.4-alpha2 07 Mar 2024 H1 M1 Apache-2.0 Yes Details →
5.3.1 21 Jan 2024 M1 Apache-2.0 Yes Details →
5.4-alpha1 26 Dec 2023 H1 M1 Apache-2.0 Yes Details →
5.3 03 Dec 2023 M1 Apache-2.0 Yes Details →
5.2.3 28 Nov 2023 M1 Apache-2.0 Yes Details →
5.2.2 19 Nov 2023 M1 Apache-2.0 Yes Details →
5.3-alpha1 15 Aug 2023 M1 Apache-2.0 Yes Details →
5.2.1 03 Dec 2022 M1 Apache-2.0 Yes Details →
5.1.4 13 Nov 2022 M1 Apache-2.0 Yes Details →
5.2 06 Nov 2022 M1 Apache-2.0 Yes Details →
5.2-beta1 03 Jun 2022 M1 Apache-2.0 Yes Details →
5.1.3 27 Jan 2022 M1 Apache-2.0 Yes Details →
5.1.2 13 Nov 2021 M1 Apache-2.0 Yes Details →
5.2-alpha1 29 Oct 2021 M1 Apache-2.0 Yes Details →
5.1.1 22 Oct 2021 M1 Apache-2.0 Yes Details →
5.1 07 May 2021 M1 Apache-2.0 Yes Details →
5.0.4 07 May 2021 M1 Apache-2.0 Yes Details →
5.1-beta1 07 Feb 2021 M1 Apache-2.0 Yes Details →
5.0.3 03 Oct 2020 M1 Apache-2.0 Yes Details →
5.0.2 23 Sep 2020 M1 Apache-2.0 Yes Details →
5.0.1 08 Jun 2020 M1 Apache-2.0 Yes Details →
5.0 19 Feb 2020 M1 Apache-2.0 Yes Details →
5.0-beta7 23 Jan 2020 M1 Apache-2.0 Yes Details →
5.0-beta6 06 Oct 2019 M1 Apache-2.0 Yes Details →
5.0-beta5 18 Jul 2019 M1 Apache-2.0 Yes Details →
5.0-beta4 03 Apr 2019 M1 Apache-2.0 Yes Details →
5.0-beta3 11 Dec 2018 M1 Apache-2.0 Yes Details →
5.0-beta2 23 Oct 2018 M1 Apache-2.0 Yes Details →
5.0-beta1 15 Jan 2018 M1 Apache-2.0 Yes Details →
5.0-alpha3 19 Nov 2017 M1 Apache-2.0 Yes Details →
5.0-alpha2 07 May 2017 M1 Apache-2.0 Yes Details →
5.0-alpha1 20 Jan 2016 M1 Apache-2.0 Yes Details →

All 51 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.httpcomponents.client5:httpclient5

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-27820: Apache HttpClient 5.4.x Domain Check Disabling Vulnerability 7.5 high 5.4.3 24 Apr 2025
CVE-2026-40542: Apache HttpClient 5.6 Vulnerability in SCRAM-SHA-256 Authentication 7.3 high 5.6.1 22 Apr 2026
CVE-2026-64607: Apache HttpComponents Client Connection Leak Due to Content-Encoding Decode Error 5.3 medium 5.6.3 31 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.httpcomponents.client5:httpclient5

Is org.apache.httpcomponents.client5:httpclient5 safe to use?

Vulert records 3 vulnerabilities for org.apache.httpcomponents.client5:httpclient5 in Maven: 0 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.httpcomponents.client5:httpclient5's Vulert package health score?

Vulert scores org.apache.httpcomponents.client5:httpclient5 87/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.httpcomponents.client5:httpclient5 affected?

No. 5.7-beta1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does org.apache.httpcomponents.client5:httpclient5 have?

3 vulnerabilities are recorded for org.apache.httpcomponents.client5:httpclient5 in the Maven ecosystem: 0 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.httpcomponents.client5:httpclient5 vulnerabilities disclosed?

2 vulnerabilities were recorded for org.apache.httpcomponents.client5:httpclient5 in the last 12 months, and the oldest entry in this database dates to 24 Apr 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.httpcomponents.client5:httpclient5 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.httpcomponents.client5:httpclient5 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.httpcomponents.client5:httpclient5 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.