Vulnerability Database · Maven · Package report

org.apache.httpcomponents:httpclient: vulnerability history, versions and safety

org.apache.httpcomponents:httpclient is a package in the Maven ecosystem. Vulert records 6 vulnerabilities for it across 53 releases, from Oct 2018 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C1 H1 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.apache.httpcomponents:httpclient 4.5.14 i

Updated on 22 Oct 2026

Good news: 4.5.14, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 81/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 4.5.14 — unaffected i
  • Vulnerabilities on record 6 over 3 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 20,470 packages i
  • Last release 46 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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:httpclient, 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
4.5.14 30 Nov 2022 none Apache-2.0 — Details →
4.5.13 03 Oct 2020 none Apache-2.0 — Details →
4.5.12 04 Mar 2020 M1 Apache-2.0 Yes Details →
4.5.11 15 Jan 2020 M1 Apache-2.0 Yes Details →
4.5.10 05 Sep 2019 M1 Apache-2.0 Yes Details →
4.5.9 07 Jun 2019 M1 Apache-2.0 Yes Details →
4.5.8 26 Mar 2019 M1 Apache-2.0 Yes Details →
4.5.7 20 Jan 2019 M1 Apache-2.0 Yes Details →
4.5.6 05 Jul 2018 M1 Apache-2.0 Yes Details →
4.5.5 18 Jan 2018 M1 Apache-2.0 Yes Details →
4.5.4 27 Nov 2017 M1 Apache-2.0 Yes Details →
4.5.3 21 Jan 2017 M1 Apache-2.0 Yes Details →
4.5.2 21 Feb 2016 M1 Apache-2.0 Yes Details →
4.5.1 11 Sep 2015 M1 Apache-2.0 Yes Details →
4.5 31 May 2015 M1 Apache-2.0 Yes Details →
4.4.1 24 Mar 2015 M1 Apache-2.0 Yes Details →
4.4 27 Jan 2015 M1 Apache-2.0 Yes Details →
4.3.6 02 Nov 2014 M1 Apache-2.0 Yes Details →
4.4-beta1 22 Sep 2014 M1 Apache-2.0 Yes Details →
4.3.5 30 Jul 2014 M2 Apache-2.0 Yes Details →
4.4-alpha1 25 Jun 2014 M1 Apache-2.0 Yes Details →
4.3.4 31 May 2014 M3 Apache-2.0 Yes Details →
4.3.3 22 Feb 2014 M3 Apache-2.0 Yes Details →
4.3.2 15 Jan 2014 M3 Apache-2.0 Yes Details →
4.3.1 03 Oct 2013 M3 non-standard Yes Details →
4.3 04 Sep 2013 C1 M3 non-standard Yes Details →
4.2.6 04 Sep 2013 M3 non-standard Yes Details →
4.3-beta2 08 Jun 2013 M3 non-standard Yes Details →
4.2.5 19 Apr 2013 M3 non-standard Yes Details →
4.3-beta1 05 Apr 2013 M3 non-standard Yes Details →
4.2.4 05 Apr 2013 M3 non-standard Yes Details →
4.3-alpha1 16 Jan 2013 M3 non-standard Yes Details →
4.2.3 10 Jan 2013 M3 non-standard Yes Details →
4.2.2 21 Oct 2012 H1 M3 non-standard Yes Details →
4.2.1 29 Jun 2012 H1 M3 non-standard Yes Details →
4.2 17 May 2012 H1 M3 non-standard Yes Details →
4.2-beta1 06 Feb 2012 H1 M3 non-standard Yes Details →
4.1.3 02 Feb 2012 H1 M3 non-standard Yes Details →
4.2-alpha1 30 Oct 2011 H1 M3 non-standard Yes Details →
4.1.2 29 Jul 2011 H1 M3 non-standard Yes Details →
4.1.1 14 Mar 2011 H1 M3 non-standard Yes Details →
4.1 17 Jan 2011 H1 M4 non-standard Yes Details →
4.1-beta1 17 Nov 2010 H1 M4 non-standard Yes Details →
4.0.3 15 Sep 2010 H1 M4 non-standard Yes Details →
4.0.2 02 Sep 2010 H1 M4 non-standard Yes Details →
4.1-alpha2 17 May 2010 H1 M4 non-standard Yes Details →
4.1-alpha1 09 Dec 2009 H1 M4 non-standard Yes Details →
4.0.1 09 Dec 2009 H1 M4 non-standard Yes Details →
4.0 11 Aug 2009 H1 M4 non-standard Yes Details →
4.0-beta2 17 Dec 2008 H1 M3 non-standard Yes Details →
4.0-beta1 28 Aug 2008 H1 M3 non-standard Yes Details →
4.0-alpha4 07 May 2008 H1 M3 non-standard Yes Details →
4.0-alpha3 25 Feb 2008 H1 M3 non-standard Yes Details →
4.0-alpha2 06 Nov 2007 H1 M3 non-standard Yes Details →
4.0-alpha1 18 Jul 2007 H1 M3 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 3
  • 2021 1
  • 2022 2

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

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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:httpclient

Is org.apache.httpcomponents:httpclient safe to use?

Vulert records 6 vulnerabilities for org.apache.httpcomponents:httpclient in Maven: 1 critical, 1 high, 4 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:httpclient's Vulert package health score?

Vulert scores org.apache.httpcomponents:httpclient 81/100, which reads as in good shape. 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:httpclient affected?

No. 4.5.14, 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.

Which version of org.apache.httpcomponents:httpclient should I use?

4.5.14 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.httpcomponents:httpclient have?

6 vulnerabilities are recorded for org.apache.httpcomponents:httpclient in the Maven ecosystem: 1 critical, 1 high, 4 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:httpclient vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.httpcomponents:httpclient in the last 12 months, and the oldest entry in this database dates to 17 Oct 2018. 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:httpclient 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:httpclient for upcoming vulnerabilities?

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