VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ovirt-engine-sdk-python: vulnerability history, versions and safety

ovirt-engine-sdk-python is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 7 releases, from Jan 2020 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
2 vulnerabilities recorded H1 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 ovirt-engine-sdk-python vulnerabilities

Vulert verdict on ovirt-engine-sdk-python 4.6.3 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 4.6.3 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Last release 12 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 ovirt-engine-sdk-python, 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.6.3 15 Oct 2025 none Apache-2.0 — Details →
4.6.2 13 May 2025 none non-standard — Details →
4.6.1 03 Mar 2023 none non-standard — Details →
4.5.2 04 Aug 2022 none non-standard — Details →
4.5.1 19 Apr 2022 none non-standard — Details →
4.5.0 27 Oct 2021 none non-standard — Details →
4.4.15 09 Aug 2021 none non-standard — Details →
4.4.14 06 Jul 2021 none non-standard — Details →
4.4.13 14 Jun 2021 none non-standard — Details →
4.4.12 27 Apr 2021 none non-standard — Details →
4.4.11 20 Apr 2021 none non-standard — Details →
4.4.10 08 Feb 2021 none non-standard — Details →
4.4.9 17 Dec 2020 none non-standard — Details →
4.4.8 07 Dec 2020 none non-standard — Details →
4.4.7 02 Nov 2020 none non-standard — Details →
4.4.6 20 Oct 2020 none non-standard — Details →
4.4.5 13 Oct 2020 none non-standard — Details →
4.4.4 02 Jul 2020 none non-standard — Details →
4.4.3 18 May 2020 none non-standard — Details →
4.3.4 23 Apr 2020 none non-standard — Details →
4.4.2 19 Mar 2020 none non-standard — Details →
4.4.1 16 Jan 2020 none non-standard — Details →
4.4.0 16 Dec 2019 none non-standard — Details →
4.3.3 22 Jul 2019 none non-standard — Details →
4.3.0 17 Jan 2019 none non-standard — Details →
4.2.9 04 Oct 2018 none non-standard — Details →
4.2.8 14 Aug 2018 none non-standard — Details →
4.2.7 07 Jun 2018 none non-standard — Details →
4.2.6 17 Apr 2018 none non-standard — Details →
4.2.5 10 Apr 2018 none non-standard — Details →
4.2.4 24 Jan 2018 none non-standard — Details →
4.2.3 17 Jan 2018 none non-standard — Details →
4.2.2 04 Dec 2017 none non-standard — Details →
4.2.1a3 02 Nov 2017 none non-standard — Details →
4.1.7 11 Oct 2017 none non-standard — Details →
4.2.1a2 27 Sep 2017 none non-standard — Details →
4.1.6 07 Jul 2017 none non-standard — Details →
4.1.5 07 Jun 2017 none non-standard — Details →
4.1.4 25 May 2017 none non-standard — Details →
4.1.3 15 Mar 2017 none non-standard — Details →
4.1.2 03 Mar 2017 none non-standard — Details →
4.1.1 02 Mar 2017 none non-standard — Details →
4.1.0 31 Jan 2017 none non-standard — Details →
4.1.0a1 09 Jan 2017 none non-standard — Details →
4.0.4 15 Nov 2016 none non-standard — Details →
4.0.3 26 Oct 2016 none non-standard — Details →
4.0.2 27 Sep 2016 none non-standard — Details →
4.0.1 06 Sep 2016 none non-standard — Details →
4.0.0 30 Aug 2016 none non-standard — Details →
3.6.9.2 29 Aug 2016 none non-standard — Details →
4.0.0a6 22 Aug 2016 none non-standard — Details →
4.0.0a5 26 Jul 2016 none non-standard — Details →
3.6.8.0 05 Jul 2016 none non-standard — Details →
4.0.0a4 01 Jul 2016 none non-standard — Details →
3.6.7.0 11 Jun 2016 none non-standard — Details →
4.0.0a3 06 Jun 2016 none non-standard — Details →
3.6.5.1 19 May 2016 none non-standard — Details →
3.6.5.2 19 May 2016 none non-standard — Details →
3.6.3.0 11 Feb 2016 none non-standard — Details →
3.6.0.3 16 Nov 2015 none non-standard — Details →
3.5.6.0 28 Oct 2015 none non-standard — Details →
3.6.0.1 10 Sep 2015 none non-standard — Details →
3.6.0.0 04 Sep 2015 none non-standard — Details →
3.5.4.0 03 Sep 2015 none non-standard — Details →
3.5.2.1 18 Mar 2015 none non-standard — Details →
3.5.2.0 26 Feb 2015 none non-standard — Details →
3.5.1.0 21 Jan 2015 none non-standard — Details →
3.5.0.8 11 Nov 2014 none non-standard — Details →
3.5.0.7 10 Sep 2014 none non-standard — Details →
3.4.4.0 09 Sep 2014 none non-standard — Details →
3.5.0.6 03 Sep 2014 none non-standard — Details →
3.5.0.5 27 Aug 2014 none non-standard — Details →
3.5.0.4 20 Aug 2014 none non-standard — Details →
3.4.3.0 18 Jul 2014 none non-standard — Details →
3.4.1.1 07 May 2014 none non-standard — Details →
3.4.0.7 16 Apr 2014 none non-standard — Details →
3.3.5.0 01 Apr 2014 H1 U1 non-standard Yes Details →
3.4.0.6 27 Mar 2014 H1 U1 non-standard Yes Details →
3.4.0.2 20 Jan 2014 H1 U1 non-standard Yes Details →
3.4.0.1.post1 25 Dec 2013 H1 U1 non-standard Yes Details →
3.3.0.8.post1 30 Oct 2013 H1 U1 non-standard Yes Details →
3.3.0.7.post1 09 Oct 2013 H1 U1 non-standard Yes Details →
3.3.0.6.post1 03 Sep 2013 H1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for ovirt-engine-sdk-python

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Improper Validation of Hostname in x.509 Certificate in ovirt-engine-sdk-python 5.9 high 3.4.0.7 17 May 2022
CVE-2014-0161: ovirt-engine-sdk-python TLS/SSL Endpoint Spoofing N/A unrated 3.4.0.7 02 Jan 2020

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 ovirt-engine-sdk-python

Is ovirt-engine-sdk-python safe to use?

Vulert records 2 vulnerabilities for ovirt-engine-sdk-python in PyPI: 0 critical, 1 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 ovirt-engine-sdk-python's Vulert package health score?

Vulert scores ovirt-engine-sdk-python 82/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 ovirt-engine-sdk-python affected?

No. 4.6.3, 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 ovirt-engine-sdk-python should I use?

4.6.3 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 ovirt-engine-sdk-python have?

2 vulnerabilities are recorded for ovirt-engine-sdk-python in the PyPI ecosystem: 0 critical, 1 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 ovirt-engine-sdk-python vulnerabilities disclosed?

0 vulnerabilities were recorded for ovirt-engine-sdk-python in the last 12 months, and the oldest entry in this database dates to 02 Jan 2020. 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 ovirt-engine-sdk-python 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 ovirt-engine-sdk-python for upcoming vulnerabilities?

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