Vulnerability Database · PyPI · Package report

python-novaclient: vulnerability history, versions and safety

python-novaclient is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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 python-novaclient 18.13.1 i

Updated on 23 Oct 2026

Good news: 18.13.1, the version you would install today, has no known vulnerabilities.

Package health score 94/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 18.13.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 177 packages i
  • Last release 1 month 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 python-novaclient, 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
18.13.1 28 Aug 2026 none Apache-2.0 — Details →
18.13.0 13 May 2026 none Apache-2.0 — Details →
18.12.0 24 Feb 2026 none Apache-2.0 — Details →
18.11.0 01 Sep 2025 none Apache-2.0 — Details →
18.10.0 10 Jul 2025 none Apache-2.0 — Details →
18.9.0 27 Feb 2025 none Apache-2.0 — Details →
18.8.0 16 Jan 2025 none Apache-2.0 — Details →
18.7.0 30 Aug 2024 none Apache-2.0 — Details →
18.6.0 12 Mar 2024 none Apache-2.0 — Details →
18.5.0 01 Mar 2024 none Apache-2.0 — Details →
18.4.0 31 Aug 2023 none Apache-2.0 — Details →
18.3.0 17 Feb 2023 none Apache-2.0 — Details →
18.2.0 17 Nov 2022 none Apache-2.0 — Details →
17.4.1 08 Sep 2022 none Apache-2.0 — Details →
18.1.0 01 Sep 2022 none Apache-2.0 — Details →
18.0.0 20 May 2022 none Apache-2.0 — Details →
17.7.0 25 Feb 2022 none Apache-2.0 — Details →
17.0.1 18 Nov 2021 none Apache-2.0 — Details →
17.6.0 03 Sep 2021 none Apache-2.0 — Details →
17.5.0 28 May 2021 none Apache-2.0 — Details →
17.4.0 11 Mar 2021 none Apache-2.0 — Details →
17.3.0 22 Jan 2021 none Apache-2.0 — Details →
17.2.1 10 Sep 2020 none Apache-2.0 — Details →
17.2.0 22 Jul 2020 none Apache-2.0 — Details →
17.1.0 22 Jun 2020 none Apache-2.0 — Details →
15.1.1 15 Jun 2020 none Apache-2.0 — Details →
17.0.0 11 Apr 2020 none Apache-2.0 — Details →
11.0.1 12 Nov 2019 none Apache-2.0 — Details →
13.0.2 12 Nov 2019 none Apache-2.0 — Details →
10.1.1 30 Oct 2019 none Apache-2.0 — Details →
16.0.0 22 Oct 2019 none Apache-2.0 — Details →
15.1.0 10 Sep 2019 none Apache-2.0 — Details →
15.0.0 02 Sep 2019 none Apache-2.0 — Details →
14.2.0 15 Jul 2019 none Apache-2.0 — Details →
13.0.1 13 Jun 2019 none Apache-2.0 — Details →
14.1.0 28 May 2019 none Apache-2.0 — Details →
14.0.0 16 May 2019 none Apache-2.0 — Details →
9.1.3 26 Apr 2019 none Apache-2.0 — Details →
13.0.0 08 Mar 2019 none Apache-2.0 — Details →
12.0.0 13 Feb 2019 none Apache-2.0 — Details →
11.1.0 24 Oct 2018 none Apache-2.0 — Details →
11.0.0 26 Jul 2018 none Apache-2.0 — Details →
10.3.0 08 Jun 2018 none Apache-2.0 — Details →
9.1.2 25 Apr 2018 none Apache-2.0 — Details →
10.2.0 20 Apr 2018 none Apache-2.0 — Details →
10.1.0 25 Jan 2018 none Apache-2.0 — Details →
10.0.0 15 Jan 2018 none Apache-2.0 — Details →
6.0.2 05 Oct 2017 none Apache-2.0 — Details →
9.1.1 04 Oct 2017 none Apache-2.0 — Details →
9.1.0 27 Jul 2017 none Apache-2.0 — Details →
9.0.1 16 Jun 2017 none Apache-2.0 — Details →
9.0.0 07 Jun 2017 none Apache-2.0 — Details →
7.1.2 07 Jun 2017 none Apache-2.0 — Details →
3.3.3 07 Jun 2017 none Apache-2.0 — Details →
6.0.1 08 May 2017 none Apache-2.0 — Details →
7.1.1 08 May 2017 none Apache-2.0 — Details →
8.0.0 06 Apr 2017 none Apache-2.0 — Details →
7.1.0 26 Jan 2017 none Apache-2.0 — Details →
7.0.0 22 Dec 2016 none Apache-2.0 — Details →
2.30.3 22 Nov 2016 none Apache-2.0 — Details →
3.3.2 14 Sep 2016 none Apache-2.0 — Details →
6.0.0 31 Aug 2016 none Apache-2.0 — Details →
5.1.0 18 Aug 2016 none Apache-2.0 — Details →
5.0.0 18 Jul 2016 none Apache-2.0 — Details →
4.1.0 16 Jun 2016 none Apache-2.0 — Details →
4.0.0 19 Apr 2016 none Apache-2.0 — Details →
3.4.0 07 Apr 2016 none Apache-2.0 — Details →
3.3.1 31 Mar 2016 none Apache-2.0 — Details →
3.3.0 02 Mar 2016 none Apache-2.0 — Details →
3.2.0 07 Jan 2016 none Apache-2.0 — Details →
2.23.3 06 Jan 2016 none Apache-2.0 — Details →
3.1.0 18 Dec 2015 none Apache-2.0 — Details →
3.0.0 18 Dec 2015 none Apache-2.0 — Details →
2.35.0 12 Nov 2015 none Apache-2.0 — Details →
2.30.2 05 Nov 2015 none Apache-2.0 — Details →
2.34.0 04 Nov 2015 none Apache-2.0 — Details →
2.33.0 27 Oct 2015 none Apache-2.0 — Details →
2.32.0 19 Oct 2015 none Apache-2.0 — Details →
2.31.0 01 Oct 2015 none Apache-2.0 — Details →
2.30.1 01 Oct 2015 none Apache-2.0 — Details →
2.30.0 21 Sep 2015 none Apache-2.0 — Details →
2.29.0 11 Sep 2015 none Apache-2.0 — Details →
2.28.1 04 Sep 2015 none Apache-2.0 — Details →
2.28.0 04 Sep 2015 none Apache-2.0 — Details →
2.27.0 02 Sep 2015 none Apache-2.0 — Details →
2.23.2 10 Aug 2015 none Apache-2.0 — Details →
2.23.1 21 Jul 2015 none Apache-2.0 — Details →
2.26.0 03 Jun 2015 none Apache-2.0 — Details →
2.25.0 12 May 2015 none Apache-2.0 — Details →
2.24.1 22 Apr 2015 none Apache-2.0 — Details →
2.24.0 21 Apr 2015 none Apache-2.0 — Details →
2.23.0 17 Mar 2015 none Apache-2.0 — Details →
2.22.0 02 Mar 2015 none Apache-2.0 — Details →
2.21.0 19 Feb 2015 none Apache-2.0 — Details →
2.20.0 20 Sep 2014 none Apache-2.0 — Details →
2.19.0 16 Sep 2014 none Apache-2.0 — Details →
2.18.1 15 Jul 2014 none Apache-2.0 — Details →
2.18.0 11 Jul 2014 none Apache-2.0 — Details →
2.17.0 07 Mar 2014 none Apache-2.0 — Details →
2.16.0 26 Feb 2014 none Apache-2.0 — Details →
2.15.0 18 Sep 2013 none — — Details →
2.14.1 07 Aug 2013 none — — Details →
2.14.0 06 Aug 2013 none — — Details →
2.13.0 02 Apr 2013 none — — Details →
2.12.0 26 Mar 2013 none — — Details →
2.11.1 16 Feb 2013 none — — Details →
2.11.0 13 Feb 2013 none — — Details →
2.10.0 29 Nov 2012 none — — Details →
2.9.0 26 Sep 2012 none — — Details →
2.8.0 06 Sep 2012 none — — Details →
2.7.0 06 Sep 2012 none — — Details →
2.6.10 30 Jun 2012 none — — Details →
2.6.0.1 10 Apr 2012 none — — Details →
2.6.0 10 Feb 2012 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for python-novaclient

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 python-novaclient

Is python-novaclient safe to use?

Vulert has no vulnerabilities on record for python-novaclient in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is python-novaclient's Vulert package health score?

Vulert scores python-novaclient 94/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 python-novaclient affected?

No. 18.13.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 python-novaclient should I use?

18.13.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 python-novaclient have?

0 vulnerabilities are recorded for python-novaclient in the PyPI ecosystem: 0 critical, 0 high, 0 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 python-novaclient vulnerabilities disclosed?

0 vulnerabilities were recorded for python-novaclient in the last 12 months. 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 python-novaclient 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 python-novaclient for upcoming vulnerabilities?

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