VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-scciclient: vulnerability history, versions and safety

python-scciclient is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 37 releases, first recorded in Sep 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 C1 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-scciclient vulnerabilities

Vulert verdict on python-scciclient 0.17.0 i

Updated on 23 Oct 2026

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

Package health score 64/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 0.17.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 02 Sep 2022 i
  • Highest CVSS 7.4 i
  • With no published fix 0 i
  • Stars 17 i
  • Last release 19 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 python-scciclient, 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
0.17.0 03 Mar 2025 none Apache-2.0 — Details →
0.16.0 22 Mar 2024 none non-standard — Details →
0.15.0 25 Aug 2023 none non-standard — Details →
0.14.0 25 Aug 2023 none non-standard — Details →
0.13.0 25 Aug 2023 none non-standard — Details →
0.9.5 17 Sep 2022 C1 U1 non-standard Yes Details →
0.8.3.dev1 12 Aug 2022 C1 U1 non-standard Yes Details →
0.8.2.dev1 12 Aug 2022 C1 U1 non-standard Yes Details →
0.9.2.dev1 12 Aug 2022 C1 U1 non-standard Yes Details →
0.8.2 10 Aug 2022 C1 U1 non-standard Yes Details →
0.8.3 10 Aug 2022 C1 U1 non-standard Yes Details →
0.9.2 10 Aug 2022 C1 U1 non-standard Yes Details →
0.12.3 29 Jul 2022 none non-standard — Details →
0.10.2 29 Jul 2022 C1 U1 non-standard Yes Details →
0.11.4 29 Jul 2022 C1 U1 non-standard Yes Details →
0.11.3 15 Jul 2022 C1 U1 non-standard Yes Details →
0.12.2 15 Jul 2022 none non-standard — Details →
0.10.1 15 Jul 2022 C1 U1 non-standard Yes Details →
0.12.1 13 Jun 2022 none non-standard — Details →
0.12.0 01 Jun 2022 none non-standard — Details →
0.9.4 19 Jan 2022 C1 U1 non-standard Yes Details →
0.11.2 18 Jan 2022 C1 U1 non-standard Yes Details →
0.9.3 06 Dec 2021 C1 U1 non-standard Yes Details →
0.11.1 06 Dec 2021 C1 U1 non-standard Yes Details →
0.11.0.dev1 03 Dec 2021 C1 U1 non-standard Yes Details →
0.9.2.dev3 03 Dec 2021 C1 U1 non-standard Yes Details →
0.10.0 20 Jul 2021 C1 U1 non-standard Yes Details →
0.9.1 22 Feb 2021 C1 U1 non-standard Yes Details →
0.9.0 17 Feb 2021 C1 U1 non-standard Yes Details →
0.7.4 22 Mar 2019 C1 U1 non-standard Yes Details →
0.8.1 22 Mar 2019 C1 U1 non-standard Yes Details →
0.8.0 30 Aug 2018 C1 U1 non-standard Yes Details →
0.7.3 10 Aug 2018 C1 U1 non-standard Yes Details →
0.6.2 27 Jul 2018 C1 U1 non-standard Yes Details →
0.7.2 18 Jul 2018 C1 U1 non-standard Yes Details →
0.7.1 11 Jul 2018 C1 U1 non-standard Yes Details →
0.7.0 15 Jun 2018 C1 U1 non-standard Yes Details →
0.6.1 26 Jan 2018 C1 U1 non-standard Yes Details →
0.6.0 13 Nov 2017 C1 U1 non-standard Yes Details →
0.5.0 27 Jul 2017 C1 U1 non-standard Yes Details →
0.3.1 05 Sep 2016 C1 U1 non-standard Yes Details →
0.4.0 31 Aug 2016 C1 U1 non-standard Yes Details →
0.3.0 04 Dec 2015 C1 U1 non-standard Yes Details →
0.2.0 23 Jul 2015 C1 U1 non-standard Yes Details →
0.1.0 01 Apr 2015 C1 U1 non-standard Yes Details →
0.0.1 27 Jan 2015 C1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-2996: python-scciclient vulnerable to Man-in-the-middle (MITM) attacks 7.4 critical 0.12.0 02 Sep 2022
CVE-2022-2996: python-scciclient HTTPS Certificate Verification Bypass Vulnerability 7.4 high 0.12.0 01 Sep 2022

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

Is python-scciclient safe to use?

Vulert records 2 vulnerabilities for python-scciclient in PyPI: 1 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-scciclient's Vulert package health score?

Vulert scores python-scciclient 64/100, which reads as usable, but worth attention. 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-scciclient affected?

No. 0.17.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-scciclient should I use?

0.17.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-scciclient have?

2 vulnerabilities are recorded for python-scciclient in the PyPI ecosystem: 1 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-scciclient vulnerabilities disclosed?

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

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