VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

commons-httpclient: vulnerability history, versions and safety

commons-httpclient is a package in the Debian ecosystem. Vulert records 9 vulnerabilities for it across 1 release, from Nov 2012 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
9 vulnerabilities recorded U9
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 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 commons-httpclient vulnerabilities

Vulert verdict on commons-httpclient i

Updated on 23 Oct 2026

Careful: one of the 9 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 9 vulnerabilities on record across 13 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 13 years · 1 in the last year i
  • Latest disclosure 31 Jul 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 i

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 holds for commons-httpclient, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
3.1-16 U1 No Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 2
  • 2014 4
  • 2015 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for commons-httpclient

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Denial of Service in Apache HttpComponents HttpClient N/A unrated 3.1-12 27 Oct 2015
Hostname Verification Bypass in Apache Commons HttpClient 3.x N/A unrated 3.1-10.1 04 Nov 2012
Hostname Verification Bypass in Apache Commons HttpClient - CVE-2012-6153 N/A unrated 3.1-10.2 04 Sep 2014
Hostname Verification Bypass in Apache HttpComponents HttpClient and HttpAsyncClient N/A unrated 3.1-11 21 Aug 2014
Critical SSL Spoofing Vulnerability in Apache Commons HttpClient N/A unrated 3.1-10.1 04 Nov 2012

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

Is commons-httpclient safe to use?

Vulert records 9 vulnerabilities for commons-httpclient in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does commons-httpclient have?

9 vulnerabilities are recorded for commons-httpclient in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new commons-httpclient vulnerabilities disclosed?

1 vulnerability was recorded for commons-httpclient in the last 12 months, and the oldest entry in this database dates to 04 Nov 2012. 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 commons-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 commons-httpclient for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the commons-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.