VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mycli: vulnerability history, versions and safety

mycli is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Oct 2023. 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 M1 U1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 mycli vulnerabilities

Vulert verdict on mycli 2.30.0 i

Updated on 23 Oct 2026

Careful: 2.30.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.30.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 20 Oct 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Depended on by 2 packages i
  • Stars 11,984 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 mycli, 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.30.0 17 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.29.6 15 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.29.5 15 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.29.4 11 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.29.3 11 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.29.2 11 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.29.1 10 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.28.2 07 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.28.1 03 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.28.0 02 Oct 2026 M1 U1 BSD-3-Clause No Details →
2.27.0 29 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.26.0 26 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.25.3 19 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.25.2 16 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.25.1 16 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.25.0 16 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.24.5 16 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.24.4 12 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.24.3 12 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.24.2 12 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.24.1 12 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.24.0 12 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.23.0 09 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.22.0 09 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.21.1 07 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.21.0 07 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.20.0 05 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.19.0 02 Sep 2026 M1 U1 BSD-3-Clause No Details →
2.18.5 31 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.18.4 29 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.18.3 29 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.18.2 29 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.18.1 29 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.18.0 29 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.17.0 25 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.16.0 22 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.15.0 20 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.14.0 15 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.13.2 12 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.13.1 11 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.13.0 11 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.12.0 08 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.11.0 07 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.10.0 05 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.9.0 01 Aug 2026 M1 U1 BSD-3-Clause No Details →
2.8.0 31 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.7.0 25 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.6.1 24 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.5.1 22 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.5.0 22 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.4.0 18 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.3.0 16 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.2.0 11 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.1.1 08 Jul 2026 M1 U1 BSD-3-Clause No Details →
2.0.0 03 Jul 2026 M1 U1 BSD-3-Clause No Details →
1.76.0 20 Jun 2026 M1 U1 BSD-3-Clause No Details →
1.75.0 20 Jun 2026 M1 U1 BSD-3-Clause No Details →
1.74.1 18 Jun 2026 M1 U1 BSD-3-Clause No Details →
1.74.0 06 Jun 2026 M1 U1 BSD-3-Clause No Details →
1.73.1 29 May 2026 M1 U1 BSD-3-Clause No Details →
1.73.0 27 May 2026 M1 U1 BSD-3-Clause No Details →
1.72.1 11 May 2026 M1 U1 BSD-3-Clause No Details →
1.72.0 08 May 2026 M1 U1 BSD-3-Clause No Details →
1.71.0 01 May 2026 M1 U1 BSD-3-Clause No Details →
1.70.0 24 Apr 2026 M1 U1 BSD-3-Clause No Details →
1.69.0 20 Apr 2026 M1 U1 BSD-3-Clause No Details →
1.68.1 16 Apr 2026 M1 U1 BSD-3-Clause No Details →
1.68.0 13 Apr 2026 M1 U1 BSD-3-Clause No Details →
1.67.1 28 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.66.0 21 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.65.1 18 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.65.0 16 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.64.0 13 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.63.0 12 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.62.0 08 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.61.0 07 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.60.0 05 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.59.0 03 Mar 2026 M1 U1 BSD-3-Clause No Details →
1.58.0 28 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.57.0 25 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.56.0 23 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.55.0 20 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.54.1 17 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.54.0 16 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.53.0 12 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.52.0 11 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.51.1 09 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.50.0 07 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.49.0 02 Feb 2026 M1 U1 BSD-3-Clause No Details →
1.48.0 27 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.47.0 24 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.46.0 22 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.45.0 20 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.44.2 13 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.44.1 10 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.44.0 08 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.43.1 03 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.43.0 02 Jan 2026 M1 U1 BSD-3-Clause No Details →
1.42.0 20 Dec 2025 M1 U1 BSD-3-Clause No Details →
1.41.2 24 Nov 2025 M1 U1 BSD-3-Clause No Details →
1.41.1 15 Nov 2025 M1 U1 — No Details →
1.41.0 01 Nov 2025 M1 U1 — No Details →
1.40.0 14 Oct 2025 M1 U1 — No Details →
1.39.1 06 Oct 2025 M1 U1 — No Details →
1.39.0 30 Sep 2025 M1 U1 — No Details →
1.38.4 06 Sep 2025 M1 U1 — No Details →
1.38.3 21 Aug 2025 M1 U1 — No Details →
1.38.2 19 Aug 2025 M1 U1 — No Details →
1.38.1 19 Aug 2025 M1 U1 — No Details →
1.38.0 16 Aug 2025 M1 U1 — No Details →
1.37.1 28 Jul 2025 M1 U1 — No Details →
1.37.0 28 Jul 2025 M1 U1 — No Details →
1.36.0 19 Jul 2025 M1 U1 — No Details →
1.35.0 18 Jul 2025 M1 U1 — No Details →
1.34.4 15 Jul 2025 M1 U1 — No Details →
1.34.3 14 Jul 2025 M1 U1 — No Details →
1.34.2 12 Jul 2025 M1 U1 — No Details →
1.34.1 12 Jul 2025 M1 U1 — No Details →
1.34.0 11 Jul 2025 M1 U1 — No Details →
1.33.0 07 Jul 2025 M1 U1 — No Details →

The newest 120 of 178 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 mycli

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-44690: Inadequate encryption strength in mycli 1.27.0 7.5 high No fix published 19 Oct 2023
Inadequate Encryption Strength in mycli N/A medium No fix published 20 Oct 2023

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 mycli

Is mycli safe to use?

Vulert records 2 vulnerabilities for mycli in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is mycli's Vulert package health score?

Vulert scores mycli 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of mycli affected?

Yes. 2.30.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of mycli should I use?

2.30.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 mycli have?

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

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

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