VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-muranoclient: vulnerability history, versions and safety

python-muranoclient is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 27 releases, first recorded in Sep 2016. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
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 python-muranoclient vulnerabilities

Vulert verdict on python-muranoclient 2.8.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Not enough data

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

  • Current release 2.8.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Sep 2016 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 12 packages i
  • Last release 31 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, 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 python-muranoclient, 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
2.8.0 01 Mar 2024 none Apache-2.0 — Details →
2.7.0 12 Sep 2023 none Apache-2.0 — Details →
2.6.0 24 Feb 2023 none Apache-2.0 — Details →
2.5.0 01 Sep 2022 none Apache-2.0 — Details →
2.4.1 22 Feb 2022 none Apache-2.0 — Details →
2.4.0 20 Oct 2021 none Apache-2.0 — Details →
2.3.0 17 Sep 2021 none Apache-2.0 — Details →
2.2.0 25 Jan 2021 none Apache-2.0 — Details →
2.1.1 10 Sep 2020 none Apache-2.0 — Details →
2.1.0 18 Jun 2020 none Apache-2.0 — Details →
2.0.1 08 Apr 2020 none Apache-2.0 — Details →
2.0.0 13 Feb 2020 none Apache-2.0 — Details →
1.3.0 09 Aug 2019 none Apache-2.0 — Details →
0.14.1 17 Apr 2019 none Apache-2.0 — Details →
1.2.0 08 Mar 2019 none Apache-2.0 — Details →
1.1.1 25 Jul 2018 none Apache-2.0 — Details →
1.1.0 11 Jul 2018 none Apache-2.0 — Details →
1.0.1 22 Jan 2018 none Apache-2.0 — Details →
1.0.0 16 Jan 2018 none Apache-2.0 — Details →
0.14.0 28 Jul 2017 none Apache-2.0 — Details →
0.13.0 07 Jun 2017 none Apache-2.0 — Details →
0.12.0 25 Jan 2017 none Apache-2.0 — Details →
0.11.1 10 Oct 2016 none Apache-2.0 — Details →
0.11.0 01 Sep 2016 none Apache-2.0 — Details →
0.8.6 01 Sep 2016 none Apache-2.0 — Details →
0.10.0 09 Aug 2016 none Apache-2.0 — Details →
0.8.5 27 Jun 2016 none Apache-2.0 — Details →
0.7.3 27 Jun 2016 none Apache-2.0 — Details →
0.9.0 27 Jun 2016 none Apache-2.0 — Details →
0.8.4 31 Mar 2016 U1 Apache-2.0 Yes Details →
0.8.3 03 Mar 2016 U1 Apache-2.0 Yes Details →
0.8.2 17 Feb 2016 U1 Apache-2.0 Yes Details →
0.8.1 18 Jan 2016 U1 Apache-2.0 Yes Details →
0.7.2 29 Dec 2015 U1 Apache-2.0 Yes Details →
0.8.0 03 Dec 2015 U1 Apache-2.0 Yes Details →
0.7.1 03 Oct 2015 U1 Apache-2.0 Yes Details →
0.7.0 04 Sep 2015 U1 Apache-2.0 Yes Details →
0.6.3 24 Aug 2015 U1 Apache-2.0 Yes Details →
0.6.2 21 Jul 2015 U1 Apache-2.0 Yes Details →
0.6.0 02 Jun 2015 U1 Apache-2.0 Yes Details →
0.5.9 30 Apr 2015 U1 Apache-2.0 Yes Details →
0.5.8 30 Apr 2015 U1 Apache-2.0 Yes Details →
0.5.7 23 Apr 2015 U1 Apache-2.0 Yes Details →
0.5.6 25 Mar 2015 U1 Apache-2.0 Yes Details →
0.5.5 10 Sep 2014 U1 Apache-2.0 Yes Details →
0.5.4 13 Aug 2014 U1 Apache-2.0 Yes Details →
0.5.3 11 Aug 2014 U1 Apache-2.0 Yes Details →
0.5.2 30 May 2014 U1 Apache-2.0 Yes Details →
0.5.1 29 Apr 2014 U1 Apache-2.0 Yes Details →
0.5.0 19 Apr 2014 U1 Apache-2.0 Yes Details →
0.4.1 07 Feb 2014 U1 Apache-2.0 Yes Details →
0.4.0 20 Dec 2013 U1 Apache-2.0 Yes Details →
0.2.12 22 Nov 2013 U1 Apache-2.0 Yes Details →
0.3.0 22 Nov 2013 U1 Apache-2.0 Yes Details →
0.2.11 01 Oct 2013 U1 Apache-2.0 Yes Details →
0.2.0 09 Sep 2013 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 1

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

03 Vulnerabilities

Recorded vulnerabilities for python-muranoclient

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-4972: OpenStack Murano Improper Use of Loaders Remote Code Execution N/A unrated 0.7.3 26 Sep 2016

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-muranoclient

Is python-muranoclient safe to use?

Vulert records 1 vulnerabilities for python-muranoclient in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 python-muranoclient's Vulert package health score?

Vulert scores python-muranoclient 79/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 python-muranoclient affected?

No. 2.8.0, 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-muranoclient should I use?

2.8.0 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-muranoclient have?

1 vulnerability is recorded for python-muranoclient in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 python-muranoclient vulnerabilities disclosed?

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

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