VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

linotp: vulnerability history, versions and safety

linotp is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 28 releases, from Jun 2019 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
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 linotp vulnerabilities

Vulert verdict on linotp 2.11.1 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 2.11.1 — unaffected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Last release 78 months ago i
  • Licence non-standard 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 linotp, 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.11.1 30 Mar 2020 none non-standard — Details →
2.10.0.1 31 Jan 2018 C1 U2 non-standard Yes Details →
2.10.0 30 Jan 2018 C1 U2 non-standard Yes Details →
2.9.3.3 20 Sep 2017 C1 U2 non-standard Yes Details →
2.9.3.2 12 Sep 2017 C1 U2 non-standard Yes Details →
2.9.3.1 04 Sep 2017 C1 U2 non-standard Yes Details →
2.9.3 14 Aug 2017 C1 U2 non-standard Yes Details →
2.9.1.4 06 Jun 2017 C1 U2 non-standard Yes Details →
2.9.1 15 Feb 2017 C1 U2 non-standard Yes Details →
2.8.1.7 15 Dec 2016 C1 U2 non-standard Yes Details →
2.9.0.5 15 Dec 2016 C1 U2 non-standard Yes Details →
2.9.0.4 05 Dec 2016 C1 U2 non-standard Yes Details →
2.9.0.3 05 Dec 2016 C1 U2 non-standard Yes Details →
2.9.0 15 Aug 2016 C1 U2 non-standard Yes Details →
2.8.1.3 30 Jul 2016 C1 U2 non-standard Yes Details →
2.8.1.2 06 Jul 2016 C1 U2 non-standard Yes Details →
2.8.1 05 Apr 2016 C1 U2 non-standard Yes Details →
2.8.0.3 08 Feb 2016 C1 U2 non-standard Yes Details →
2.8.0.2 14 Jan 2016 C1 U2 non-standard Yes Details →
2.8.0.1 08 Dec 2015 C1 U2 non-standard Yes Details →
2.8.0 27 Nov 2015 C1 U2 non-standard Yes Details →
2.7.2.2 09 Nov 2015 C1 U2 non-standard Yes Details →
2.7.2.1 15 Jul 2015 C1 U2 non-standard Yes Details →
2.7.2 12 May 2015 C1 U2 non-standard Yes Details →
2.7.1.2 19 Feb 2015 C1 U2 non-standard Yes Details →
2.7.1.1 26 Jan 2015 C1 U2 non-standard Yes Details →
2.7.1 20 Jan 2015 C1 U2 non-standard Yes Details →
2.7.0.2 08 Aug 2014 C1 U2 non-standard Yes Details →
2.7.0 20 May 2014 C1 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2022 1

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 linotp

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-12887: LinOTP replay vulnerability with auto resynchronization enabled for TOTP token 8.1 critical 2.11.1 24 May 2022
CVE-2019-12887: Incorrect Access Control in KeyIdentity LinOTP N/A unrated 2.11.1 27 Jun 2019
CVE-2019-12887: KeyIdentity LinOTP Incorrect Access Control N/A unrated 2.11.1 27 Jun 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 linotp

Is linotp safe to use?

Vulert records 3 vulnerabilities for linotp 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 linotp's Vulert package health score?

Vulert scores linotp 61/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 linotp affected?

No. 2.11.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 linotp should I use?

2.11.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 linotp have?

3 vulnerabilities are recorded for linotp 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 linotp vulnerabilities disclosed?

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

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