VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

apache-libcloud: vulnerability history, versions and safety

apache-libcloud is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 17 releases, from Sep 2011 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 H1 M1 L1 U3
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.

See all apache-libcloud vulnerabilities

Vulert verdict on apache-libcloud 3.9.1 i

Updated on 22 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.9.1 — unaffected i
  • Vulnerabilities on record 6 over 10 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 202 packages i
  • Stars 2,127 i
  • OpenSSF scorecard 6/10 i
  • Last release 6 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, 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 apache-libcloud, 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
3.9.1 21 Apr 2026 none Apache-2.0 — Details →
3.9.0 09 Feb 2026 none Apache-2.0 — Details →
3.8.0 10 Aug 2023 none Apache-2.0 — Details →
3.7.0 08 Jan 2023 none Apache-2.0 — Details →
3.6.1 10 Oct 2022 none Apache-2.0 — Details →
3.6.0 26 May 2022 none Apache-2.0 — Details →
3.5.1 30 Mar 2022 none Apache-2.0 — Details →
3.5.0 11 Mar 2022 none Apache-2.0 — Details →
3.4.1 15 Nov 2021 none Apache-2.0 — Details →
3.4.0 11 Nov 2021 none Apache-2.0 — Details →
3.3.1 25 Jan 2021 none Apache-2.0 — Details →
3.3.0 02 Jan 2021 none Apache-2.0 — Details →
3.2.0 20 Sep 2020 none Apache-2.0 — Details →
2.8.3 12 Jun 2020 none Apache-2.0 — Details →
3.1.0 12 Jun 2020 none Apache-2.0 — Details →
3.0.0 15 Apr 2020 none Apache-2.0 — Details →
2.8.2 15 Apr 2020 none Apache-2.0 — Details →
2.8.1 03 Mar 2020 none Apache-2.0 — Details →
3.0.0rc1 29 Jan 2020 none Apache-2.0 — Details →
2.8.0 02 Jan 2020 none Apache-2.0 — Details →
2.7.0 09 Dec 2019 none Apache-2.0 — Details →
2.6.1 18 Nov 2019 none Apache-2.0 — Details →
2.6.0 28 Aug 2019 none Apache-2.0 — Details →
2.5.0 30 May 2019 none Apache-2.0 — Details →
2.4.0 10 Nov 2018 none Apache-2.0 — Details →
2.3.0 03 Mar 2018 none Apache-2.0 — Details →
2.2.1 21 Sep 2017 none Apache-2.0 — Details →
2.2.0 03 Sep 2017 none Apache-2.0 — Details →
2.1.0 17 Jul 2017 none Apache-2.0 — Details →
2.0.0 25 Apr 2017 none Apache-2.0 — Details →
2.0.0rc2 07 Apr 2017 none Apache-2.0 — Details →
1.5.0 29 Dec 2016 none Apache-2.0 — Details →
1.4.0 26 Nov 2016 none Apache-2.0 — Details →
1.3.0 14 Oct 2016 none Apache-2.0 — Details →
1.2.1 22 Sep 2016 none Apache-2.0 — Details →
1.1.0 06 Jul 2016 none Apache-2.0 — Details →
1.0.0 20 Jun 2016 none Apache-2.0 — Details →
1.0.0rc2 11 Apr 2016 none Apache-2.0 — Details →
1.0.0rc1 25 Jan 2016 none Apache-2.0 — Details →
0.20.1 19 Jan 2016 none Apache-2.0 — Details →
0.20.0 16 Dec 2015 none Apache-2.0 — Details →
0.19.0 30 Oct 2015 none Apache-2.0 — Details →
0.18.0 13 Aug 2015 none Apache-2.0 — Details →
0.17.0 18 Feb 2015 none Apache-2.0 — Details →
0.16.0 11 Nov 2014 none Apache-2.0 — Details →
0.15.1 10 Jul 2014 none Apache-2.0 — Details →
0.15.0 25 Jun 2014 none Apache-2.0 — Details →
0.14.1 08 Feb 2014 none Apache-2.0 — Details →
0.14.0 22 Jan 2014 none Apache-2.0 — Details →
0.13.3 31 Dec 2013 none Apache-2.0 — Details →
0.13.2 12 Dec 2013 L1 U1 Apache-2.0 Yes Details →
0.14.0b3 21 Nov 2013 none Apache-2.0 — Details →
0.13.1 05 Sep 2013 L1 U1 Apache-2.0 Yes Details →
0.13.0 01 Jul 2013 L1 U1 Apache-2.0 Yes Details →
0.12.4 25 Jun 2013 L1 U1 Apache-2.0 Yes Details →
0.4.0 22 Nov 2010 M1 U2 Apache-2.0 Yes Details →
0.3.1 11 May 2010 H1 M1 U2 Apache-2.0 Yes Details →
0.10.1 — M1 U1 — Yes Details →
0.11.0 — M1 U1 — Yes Details →
0.11.1 — none — — Details →
0.11.3 — none — — Details →
0.11.4 — none — — Details →
0.12.1 — none — — Details →
0.12.3 — L1 U1 — Yes Details →
0.4.2 — M1 U1 — Yes Details →
0.5.0 — M1 U1 — Yes Details →
0.5.2 — M1 U1 — Yes Details →
0.6.1 — M1 U1 — Yes Details →
0.6.2 — M1 U1 — Yes Details →
0.7.1 — M1 U1 — Yes Details →
0.8.0 — M1 U1 — Yes Details →
0.9.1 — M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 1
  • 2012 1
  • 2014 1
  • 2022 3

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.

03 Vulnerabilities

Recorded vulnerabilities for apache-libcloud

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2010-4340: Apache Libcloud SSL Certificate Verification Bypass 7.5 high 0.4.0 17 May 2022
Apache Libcloud Vulnerable to Certificate Impersonation 5.9 medium 0.11.1 17 May 2022
CVE-2010-4340: SSL Certificate Verification Bypass in apache-libcloud N/A unrated 0.4.2 12 Sep 2011
CVE-2012-3446: Apache Libcloud SSL Server Spoofing N/A unrated 0.11.1 04 Nov 2012
CVE-2013-6480: Vulnerability in apache-libcloud N/A unrated 0.13.3 07 Jan 2014

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 apache-libcloud

Is apache-libcloud safe to use?

Vulert records 6 vulnerabilities for apache-libcloud in PyPI: 0 critical, 1 high, 1 medium and 1 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is apache-libcloud's Vulert package health score?

Vulert scores apache-libcloud 83/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 apache-libcloud affected?

No. 3.9.1, 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 apache-libcloud should I use?

3.9.1 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 apache-libcloud have?

6 vulnerabilities are recorded for apache-libcloud in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 1 low, plus 3 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 apache-libcloud vulnerabilities disclosed?

0 vulnerabilities were recorded for apache-libcloud in the last 12 months, and the oldest entry in this database dates to 12 Sep 2011. 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 apache-libcloud 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 apache-libcloud for upcoming vulnerabilities?

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