Vulnerability Database · PyPI · Package report

openslides: vulnerability history, versions and safety

openslides is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 28 releases, from Dec 2020 to Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded U3
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.

Vulert verdict on openslides 3.3.0 i

Updated on 23 Oct 2026

Careful: 3.3.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 54/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

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 3.3.0 — affected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 25 Sep 2024 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Last release 70 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 openslides, 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
3.3.0 18 Dec 2020 U2 MIT No Details →
3.2.0 15 Jul 2020 U2 MIT No Details →
3.1.0 13 Dec 2019 U2 MIT No Details →
3.0.0 13 Sep 2019 U2 MIT No Details →
2.3.0 20 Sep 2018 U2 MIT No Details →
2.3.0b1 30 Aug 2018 U2 MIT No Details →
2.2.0 06 Jun 2018 U2 MIT No Details →
2.2.0b3 13 Apr 2018 U2 MIT No Details →
2.2.0b2 16 Feb 2018 U2 MIT No Details →
2.2.0b1 20 Dec 2017 U2 MIT No Details →
2.1.1 05 Apr 2017 U3 MIT No Details →
2.1.0 29 Mar 2017 U2 MIT No Details →
2.1.0b4 07 Mar 2017 U2 MIT No Details →
2.1.0b3 10 Feb 2017 U2 MIT No Details →
2.1.0b2 26 Jan 2017 U2 MIT No Details →
2.1.0b1 16 Dec 2016 U2 MIT No Details →
2.0.0 17 Apr 2016 U2 MIT No Details →
1.7.0 16 Feb 2015 U2 MIT No Details →
1.6.1 08 Dec 2014 U3 MIT No Details →
1.6.0 02 Jun 2014 U2 MIT No Details →
1.5.1 31 Mar 2014 U3 MIT No Details →
1.5.0 25 Nov 2013 U2 MIT No Details →
1.4.2 10 Sep 2013 U3 non-standard No Details →
1.4.1 29 Jul 2013 U3 non-standard No Details →
1.4.0 08 Jul 2013 U2 non-standard No Details →
1.3.1 09 Jan 2013 U3 non-standard No Details →
1.3.0 10 Dec 2012 U2 non-standard No Details →
1.3.0rc1 27 Nov 2012 U2 non-standard No Details →

All 28 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
  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for openslides

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →

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 openslides

Is openslides safe to use?

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

What is openslides's Vulert package health score?

Vulert scores openslides 54/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 openslides affected?

Yes. 3.3.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 openslides should I use?

3.3.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 openslides have?

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

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

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