VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

limnoria: vulnerability history, versions and safety

limnoria is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, first recorded in Nov 2019. 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 C1 U2
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 limnoria vulnerabilities

Vulert verdict on limnoria 2026.10.4 i

Updated on 23 Oct 2026

Action needed: 2026.10.4 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 2026.10.4 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 20 Nov 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 675 i
  • OpenSSF scorecard 1/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 limnoria, 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
2026.10.4 18 Oct 2026 U2 BSD-3-Clause Yes Details →
2026.5.8 08 May 2026 U2 BSD-3-Clause Yes Details →
2026.3.21 25 Mar 2026 U2 BSD-3-Clause Yes Details →
2026.1.16 16 Jan 2026 U2 BSD-3-Clause Yes Details →
2025.11.2 02 Nov 2025 U2 non-standard Yes Details →
2025.7.18 18 Jul 2025 U2 non-standard Yes Details →
2025.5.3 03 May 2025 U2 non-standard Yes Details →
2024.12.20 22 Dec 2024 U2 non-standard Yes Details →
2024.10.19 19 Oct 2024 U2 non-standard Yes Details →
2024.8.26 28 Aug 2024 U2 non-standard Yes Details →
2024.7.24 25 Jul 2024 U2 non-standard Yes Details →
2024.5.30 31 May 2024 U2 non-standard Yes Details →
2024.4.26 05 May 2024 U2 non-standard Yes Details →
2023.11.18 09 Dec 2023 U2 non-standard Yes Details →
2023.9.24 24 Sep 2023 U2 non-standard Yes Details →
2023.9.22 24 Sep 2023 U2 non-standard Yes Details →
2023.8.10 10 Aug 2023 U2 non-standard Yes Details →
2023.5.27 27 May 2023 U2 non-standard Yes Details →
2023.4.28 18 May 2023 U2 non-standard Yes Details →
2023.1.28 11 Feb 2023 U2 non-standard Yes Details →
2023.1.12 12 Jan 2023 U2 non-standard Yes Details →
2022.11.10 16 Nov 2022 U2 non-standard Yes Details →
2022.9.20 27 Sep 2022 U2 non-standard Yes Details →
2022.8.7 14 Aug 2022 U2 non-standard Yes Details →
2022.6.23 03 Jul 2022 U2 non-standard Yes Details →
2022.4.27 27 Apr 2022 U2 non-standard Yes Details →
2022.4.22 26 Apr 2022 U2 non-standard Yes Details →
2022.3.17 19 Mar 2022 U2 non-standard Yes Details →
2022.2.3 03 Feb 2022 U2 non-standard Yes Details →
2022.1.29 29 Jan 2022 U2 non-standard Yes Details →
2022.1.1.post1 05 Jan 2022 U2 non-standard Yes Details →
2022.1.1 01 Jan 2022 U2 non-standard Yes Details →
2021.11.20 20 Nov 2021 U2 non-standard Yes Details →
2021.11.9 18 Nov 2021 U2 non-standard Yes Details →
2021.10.9 09 Oct 2021 U2 non-standard Yes Details →
2021.7.21 31 Jul 2021 U2 non-standard Yes Details →
2021.6.15 17 Jun 2021 U2 non-standard Yes Details →
2021.5.26 27 May 2021 U2 non-standard Yes Details →
2021.5.24 24 May 2021 U2 non-standard Yes Details →
2021.5.22 23 May 2021 U2 non-standard Yes Details →
2021.4.11 11 Apr 2021 U2 non-standard Yes Details →
2021.4.1 01 Apr 2021 U2 non-standard Yes Details →
2021.3.18 26 Mar 2021 U2 non-standard Yes Details →
2021.3.13 17 Mar 2021 U2 non-standard Yes Details →
2021.1.15 24 Jan 2021 U2 non-standard Yes Details →
2020.12.5 07 Dec 2020 U2 non-standard Yes Details →
2020.10.10 13 Oct 2020 U2 non-standard Yes Details →
2020.8.30 03 Sep 2020 U2 non-standard Yes Details →
2020.8.29 30 Aug 2020 U2 non-standard Yes Details →
2020.7.1 01 Jul 2020 U2 non-standard Yes Details →
2020.4.11 01 May 2020 U2 non-standard Yes Details →
2020.3.17 19 Mar 2020 U2 non-standard Yes Details →
2020.1.31 31 Jan 2020 U2 non-standard Yes Details →
2020.1.9 09 Jan 2020 U2 non-standard Yes Details →
2020.1.1 01 Jan 2020 U2 non-standard Yes Details →
2019.12.15 21 Dec 2019 U2 non-standard Yes Details →
2019.11.22 23 Nov 2019 U2 non-standard Yes Details →
2019.11.9 09 Nov 2019 U2 non-standard Yes Details →
2019.10.22 26 Oct 2019 C1 U2 non-standard Yes Details →
2019.9.8 08 Sep 2019 C1 U2 non-standard Yes Details →
2019.8.25 25 Aug 2019 C1 U2 non-standard Yes Details →
2019.5.28 17 Jul 2019 C1 U2 non-standard Yes Details →
2019.2.23 22 Feb 2019 C1 U2 non-standard Yes Details →
2019.2.22 21 Feb 2019 C1 U2 non-standard Yes Details →
2019.2.21.1 21 Feb 2019 C1 U2 non-standard Yes Details →
2019.2.21 21 Feb 2019 C1 U2 non-standard Yes Details →
2019.2.14 21 Feb 2019 C1 U2 non-standard Yes Details →
2018.12.19 24 Dec 2018 C1 U2 non-standard Yes Details →
2018.9.9 10 Sep 2018 C1 U2 non-standard Yes Details →
2018.9.1 08 Sep 2018 C1 U2 non-standard Yes Details →
2018.6.25 25 Jun 2018 C1 U2 non-standard Yes Details →
2018.6.20 25 Jun 2018 C1 U2 non-standard Yes Details →
2018.4.14 21 Apr 2018 C1 U2 non-standard Yes Details →
2018.1.25 28 Jan 2018 C1 U2 non-standard Yes Details →
2017.10.1 25 Oct 2017 C1 U2 non-standard Yes Details →
2017.8.18 18 Aug 2017 C1 U2 non-standard Yes Details →
2017.8.3 09 Aug 2017 C1 U2 non-standard Yes Details →
2017.3.30 16 Apr 2017 C1 U2 non-standard Yes Details →
2017.1.10 26 Jan 2017 C1 U2 non-standard Yes Details →
2016.12.8 08 Dec 2016 C1 U2 non-standard Yes Details →
2016.11.28 01 Dec 2016 C1 U2 non-standard Yes Details →
2016.10.2 02 Oct 2016 C1 U2 non-standard Yes Details →
2016.10.1 02 Oct 2016 C1 U2 non-standard Yes Details →
2016.9.26 26 Sep 2016 C1 U2 non-standard Yes Details →
2016.8.7 07 Aug 2016 C1 U2 non-standard Yes Details →
2016.6.29 29 Jun 2016 C1 U2 non-standard Yes Details →
2016.6.27 27 Jun 2016 C1 U2 non-standard Yes Details →
2016.5.6 06 May 2016 C1 U2 non-standard Yes Details →
2016.3.21.2 24 Mar 2016 C1 U2 non-standard Yes Details →
2016.3.21.1 24 Mar 2016 C1 U2 non-standard Yes Details →
2016.2.24 24 Feb 2016 C1 U2 non-standard Yes Details →
2016.2.23 23 Feb 2016 C1 U2 non-standard Yes Details →
2016.1.5 06 Jan 2016 C1 U2 non-standard Yes Details →
2015.12.12 12 Dec 2015 C1 U2 non-standard Yes Details →
2015.11.30 01 Dec 2015 C1 U2 non-standard Yes Details →
2015.10.4 10 Oct 2015 C1 U2 non-standard Yes Details →
2015.9.16 23 Sep 2015 C1 U2 non-standard Yes Details →
2015.8.29 29 Aug 2015 C1 U2 non-standard Yes Details →
2015.8.17 22 Aug 2015 C1 U2 non-standard Yes Details →
2015.7.8 27 Jul 2015 C1 U2 non-standard Yes Details →
2015.5.20 20 May 2015 C1 U2 — Yes Details →
2015.4.29 19 May 2015 C1 U2 — Yes Details →
2015.3.10 26 Mar 2015 C1 U2 — Yes Details →
2014.12.22 24 Dec 2014 C1 U2 — Yes Details →
2014.12.7 11 Dec 2014 C1 U2 — Yes Details →
2014.11.24 06 Dec 2014 C1 U2 — Yes Details →
2014.10.9 09 Oct 2014 C1 U2 — Yes Details →
2014.7.19 21 Jul 2014 C1 U2 — Yes Details →
2014.6.26 26 Jun 2014 C1 U2 — Yes Details →
2014.6.4 08 Jun 2014 C1 U2 — Yes Details →
2014.5.29 29 May 2014 C1 U2 — Yes Details →
2014.5.8 17 May 2014 C1 U2 — Yes Details →
2014.5.17 17 May 2014 C1 U2 — Yes Details →
2014.3.3 03 Mar 2014 C1 U2 — Yes Details →
2014-01-12T15-52-10 12 Jan 2014 C1 U2 — Yes Details →
2013-12-23T17-51-15 12 Jan 2014 C1 U2 — Yes Details →
2013-09-11T19-27-10 12 Sep 2013 C1 U2 — Yes Details →
2013-08-12T21:48:56+0200 13 Aug 2013 C1 U2 — Yes Details →
2013-07-19T09:11:08+0000 30 Jul 2013 C1 U2 — Yes Details →
2013-06-01T10:32:51+0200 01 Jun 2013 C1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3

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 limnoria

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-19010: Eval Injection in Supybot/Limnoria 9.8 critical 2019.11.09 20 Nov 2019
CVE-2019-19010: Eval Injection in Limnoria Math Plugin N/A unrated 3848ae78de45b35c029cc333963d436b9d2f0a35 16 Nov 2019
CVE-2019-19010: Eval Injection in Limnoria Math Plugin N/A unrated 3848ae78de45b35c029cc333963d436b9d2f0a35 16 Nov 2019

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 limnoria

Is limnoria safe to use?

Vulert records 3 vulnerabilities for limnoria in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 2 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 limnoria's Vulert package health score?

Vulert scores limnoria 68/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 limnoria affected?

Yes. 2026.10.4, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of limnoria should I use?

2026.10.4 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 limnoria have?

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

0 vulnerabilities were recorded for limnoria in the last 12 months, and the oldest entry in this database dates to 16 Nov 2019. 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 limnoria 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 limnoria for upcoming vulnerabilities?

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