VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ops-cli: vulnerability history, versions and safety

ops-cli is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 19 releases, from Oct 2021 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 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 ops-cli vulnerabilities

Vulert verdict on ops-cli 2.4.1 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 2.4.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 203 i
  • OpenSSF scorecard 6/10 i
  • Last release 8 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 ops-cli, 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.4.1 03 Feb 2026 none Apache-2.0 — Details →
2.4.0 03 Feb 2026 none Apache-2.0 — Details →
2.3.2 12 Nov 2025 none Apache-2.0 — Details →
2.3.1 15 Jan 2025 none Apache-2.0 — Details →
2.3.0 15 Jan 2025 none Apache-2.0 — Details →
2.2.1 12 Oct 2023 none Apache-2.0 — Details →
2.2.0 01 Aug 2023 none Apache-2.0 — Details →
2.1.7 14 Oct 2021 none Apache-2.0 — Details →
2.1.6 14 Oct 2021 none Apache-2.0 — Details →
2.1.5 13 Sep 2021 none Apache-2.0 — Details →
2.1.4 13 Sep 2021 none Apache-2.0 — Details →
2.1.3 13 Sep 2021 none Apache-2.0 — Details →
2.1.2 13 Sep 2021 none Apache-2.0 — Details →
2.1.1 13 Sep 2021 none Apache-2.0 — Details →
2.1.0 13 Sep 2021 none Apache-2.0 — Details →
2.0.11 01 Sep 2021 none Apache-2.0 — Details →
2.0.10 01 Sep 2021 none Apache-2.0 — Details →
2.0.9 01 Sep 2021 none Apache-2.0 — Details →
2.0.8 01 Sep 2021 none Apache-2.0 — Details →
2.0.7 01 Sep 2021 none Apache-2.0 — Details →
2.0.6 01 Sep 2021 none Apache-2.0 — Details →
2.0.4 16 Dec 2019 C1 U1 Apache-2.0 Yes Details →
1.12.2 12 Nov 2019 C1 U1 Apache-2.0 Yes Details →
1.12.1 12 Nov 2019 C1 U1 Apache-2.0 Yes Details →
2.0.3 12 Nov 2019 C1 U1 Apache-2.0 Yes Details →
1.11.12 05 Nov 2019 C1 U1 Apache-2.0 Yes Details →
1.11.11 23 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.10 23 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.9 23 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.8 18 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.7 17 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.6 07 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.5 04 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.4 04 Oct 2019 C1 U1 Apache-2.0 Yes Details →
1.11.3 10 Sep 2019 C1 U1 Apache-2.0 Yes Details →
1.11.2 29 Aug 2019 C1 U1 Apache-2.0 Yes Details →
1.11.1 29 Aug 2019 C1 U1 Apache-2.0 Yes Details →
1.11.0 29 Aug 2019 C1 U1 Apache-2.0 Yes Details →
1.10.1 29 Aug 2019 C1 U1 Apache-2.0 Yes Details →
1.10.0 27 Aug 2019 C1 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 ops-cli

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2021-40720: Ops CLI Deserialization of Untrusted Data vulnerability 9.8 critical 2.0.5 24 May 2022
CVE-2021-40720: ops-cli Deserialization of Untrusted Data Vulnerability N/A unrated 2.0.5 15 Oct 2021

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 ops-cli

Is ops-cli safe to use?

Vulert records 2 vulnerabilities for ops-cli 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 ops-cli's Vulert package health score?

Vulert scores ops-cli 69/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 ops-cli affected?

No. 2.4.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 ops-cli should I use?

2.4.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 ops-cli have?

2 vulnerabilities are recorded for ops-cli 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 ops-cli vulnerabilities disclosed?

0 vulnerabilities were recorded for ops-cli in the last 12 months, and the oldest entry in this database dates to 15 Oct 2021. 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 ops-cli 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 ops-cli for upcoming vulnerabilities?

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