VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

simiki: vulnerability history, versions and safety

simiki is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 60 releases, from Aug 2021 to Sep 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 M1 U2
i
1 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 simiki vulnerabilities

Vulert verdict on simiki 1.6.2.3 i

Updated on 23 Oct 2026

Careful: 1.6.2.3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 52/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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 1.6.2.3 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 01 Sep 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 1,147 i
  • OpenSSF scorecard 1/10 i
  • Last release 89 months ago i
  • Licence MIT 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 simiki, 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
1.6.2.3 11 May 2019 U1 MIT No Details →
1.6.2.2 21 Apr 2019 U1 MIT No Details →
1.6.2.1 05 Jun 2017 C1 M1 U2 MIT No Details →
1.6.2 02 Jun 2017 C1 M1 U2 MIT No Details →
1.6.0.1 30 Jun 2016 C1 M1 U2 MIT No Details →
1.6.0 09 Jun 2016 C1 M1 U2 MIT No Details →
1.5.1 10 Apr 2016 C1 M1 U2 MIT No Details →
1.4.1 29 Aug 2015 C1 M1 U2 MIT No Details →
1.4.0 12 Aug 2015 C1 M1 U2 MIT No Details →
1.3.0 04 Mar 2015 C1 M1 U2 MIT No Details →
1.2.4 23 Dec 2014 C1 M1 U2 MIT No Details →
1.2.3 14 Sep 2014 C1 M1 U2 MIT No Details →
1.2.2 21 Aug 2014 C1 M1 U2 MIT No Details →
1.2.1 13 Jul 2014 C1 M1 U2 MIT No Details →
1.2.0 06 Jul 2014 C1 M1 U2 MIT No Details →
1.1.0 04 Jul 2014 C1 M1 U2 MIT No Details →
1.0.3 10 Jun 2014 C1 M1 U2 MIT No Details →
1.0.2 10 Jun 2014 C1 M1 U2 MIT No Details →
1.0.1 10 Jun 2014 C1 M1 U2 MIT No Details →
1.0.0 27 May 2014 C1 M1 U2 MIT No Details →
0.5.0 30 Apr 2014 C1 M1 U2 MIT No Details →
0.4.1 28 Apr 2014 C1 M1 U2 MIT No Details →
0.4.0 20 Apr 2014 C1 M1 U2 MIT No Details →
0.3.1 13 Apr 2014 C1 M1 U2 MIT No Details →
0.3.0 06 Apr 2014 C1 M1 U2 MIT No Details →
0.2.2 29 Mar 2014 C1 M1 U2 MIT No Details →
0.2.1 22 Mar 2014 C1 M1 U2 MIT No Details →
0.2.0 19 Mar 2014 C1 M1 U2 MIT No Details →
0.1.0 08 Dec 2013 C1 M1 U2 MIT No Details →
0.1.0-py2.7 — C1 M1 U2 — No Details →
0.2.0-py2.7 — C1 M1 U2 — No Details →
0.2.1-py2.7 — C1 M1 U2 — No Details →
0.2.2-py2.7 — C1 M1 U2 — No Details →
0.3.0-py2.7 — C1 M1 U2 — No Details →
0.3.1-py2.7 — C1 M1 U2 — No Details →
0.4.0-py2.7 — C1 M1 U2 — No Details →
0.4.1-py2.7 — C1 M1 U2 — No Details →
0.5.0-py2.7 — C1 M1 U2 — No Details →
1.0.0-py2.7 — C1 M1 U2 — No Details →
1.0.1-py2.7 — C1 M1 U2 — No Details →
1.0.2-py2.7 — C1 M1 U2 — No Details →
1.0.3-py2.7 — C1 M1 U2 — No Details →
1.1-py2.7 — C1 M1 U2 — No Details →
1.2-py2.7 — C1 M1 U2 — No Details →
1.2.1-py2.7 — C1 M1 U2 — No Details →
1.2.2-py2.7 — C1 M1 U2 — No Details →
1.2.3-py2.7 — C1 M1 U2 — No Details →
1.2.4-py2.7 — C1 M1 U2 — No Details →
1.3-py2.7 — C1 M1 U2 — No Details →
1.4-py2.7 — C1 M1 U2 — No Details →
1.4.1-py2.7 — C1 M1 U2 — No Details →
1.5.0.post1 — C1 M1 U2 MIT No Details →
1.5.0_1-py2.7 — C1 M1 U2 — No Details →
1.5.1-py2.7 — C1 M1 U2 — No Details →
1.6.0-py2.7 — C1 M1 U2 — No Details →
1.6.0.1-py2.7 — C1 M1 U2 — No Details →
1.6.2-py2.7 — U1 — No Details →
1.6.2.1-py2.7 — C1 M1 U2 — No Details →
1.6.2.2-py2.7 — U1 — No Details →
1.6.2.3-py2.7 — U1 — No Details →

All 60 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 4

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

03 Vulnerabilities

Recorded vulnerabilities for simiki

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-19001: Command Injection in Simiki 9.8 critical 1.6.2.2 01 Sep 2021
CVE-2020-19000: Cross Site Scripting (XSS) in Simiki 6.1 medium 1.6.2.2 01 Sep 2021
CVE-2020-19000: Cross Site Scripting (XSS) in Simiki v1.6.2.1 N/A unrated No fix published 27 Aug 2021
CVE-2020-19001: Command Injection in Simiki N/A unrated 1.6.2.2 27 Aug 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 simiki

Is simiki safe to use?

Vulert records 4 vulnerabilities for simiki in PyPI: 1 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is simiki's Vulert package health score?

Vulert scores simiki 52/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 simiki affected?

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

Which version of simiki should I use?

1.6.2.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 simiki have?

4 vulnerabilities are recorded for simiki in the PyPI ecosystem: 1 critical, 0 high, 1 medium and 0 low, plus 2 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 simiki vulnerabilities disclosed?

0 vulnerabilities were recorded for simiki in the last 12 months, and the oldest entry in this database dates to 27 Aug 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 simiki 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 simiki for upcoming vulnerabilities?

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