VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

lektor: vulnerability history, versions and safety

lektor is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 32 releases, first recorded in Mar 2024. 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 C1 U1
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 lektor vulnerabilities

Vulert verdict on lektor 3.3.14 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.3.14 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 27 Mar 2024 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 16 packages i
  • Stars 3,950 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 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 lektor, 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.14 07 Aug 2026 none non-standard — Details →
3.4.0b15 07 Aug 2026 none non-standard — Details →
3.4.0b14 05 Apr 2026 none non-standard — Details →
3.4.0b13 11 Feb 2026 none non-standard — Details →
3.3.13 11 Feb 2026 none non-standard — Details →
3.3.12 18 Aug 2024 none non-standard — Details →
3.4.0b12 04 Jun 2024 none non-standard — Details →
3.4.0b11 27 Feb 2024 none non-standard — Details →
3.3.11 27 Feb 2024 none non-standard — Details →
3.4.0b10 08 Jan 2024 none non-standard — Details →
3.4.0b9 12 Nov 2023 none non-standard — Details →
3.4.0b8 06 Jun 2023 none non-standard — Details →
3.4.0b7 05 Jun 2023 none non-standard — Details →
3.4.0b6 06 May 2023 none non-standard — Details →
3.3.10 05 May 2023 C1 U1 non-standard Yes Details →
3.3.9 16 Apr 2023 C1 U1 non-standard Yes Details →
3.4.0b5 09 Mar 2023 none non-standard — Details →
3.3.8 28 Feb 2023 C1 U1 non-standard Yes Details →
3.4.0b4 05 Nov 2022 none non-standard — Details →
3.4.0b3 20 Oct 2022 none non-standard — Details →
3.3.7 21 Sep 2022 C1 U1 non-standard Yes Details →
3.4.0b2 31 Aug 2022 none non-standard — Details →
3.4.0b1 03 Aug 2022 none non-standard — Details →
3.3.6 27 Jul 2022 C1 U1 non-standard Yes Details →
3.3.5 18 Jul 2022 C1 U1 non-standard Yes Details →
3.3.4 02 May 2022 C1 U1 non-standard Yes Details →
3.3.3 29 Mar 2022 C1 U1 non-standard Yes Details →
3.3.2 01 Mar 2022 C1 U1 non-standard Yes Details →
3.3.1 09 Jan 2022 C1 U1 non-standard Yes Details →
3.3.0 14 Dec 2021 C1 U1 non-standard Yes Details →
3.2.3 11 Dec 2021 C1 U1 non-standard Yes Details →
3.2.2 18 Sep 2021 C1 U1 non-standard Yes Details →
3.2.1 18 Sep 2021 C1 U1 non-standard Yes Details →
3.2.0 20 Aug 2020 C1 U1 non-standard Yes Details →
3.2.0.dev0 14 Aug 2020 C1 U1 non-standard Yes Details →
3.1.3 26 Jan 2019 C1 U1 non-standard Yes Details →
3.1.2 07 Sep 2018 C1 U1 non-standard Yes Details →
3.1.1 18 Apr 2018 C1 U1 non-standard Yes Details →
3.1.0 29 Jan 2018 C1 U1 non-standard Yes Details →
3.1.0.dev1 09 Dec 2017 C1 U1 non-standard Yes Details →
3.0.1 12 Jun 2017 C1 U1 non-standard Yes Details →
3.0.0 12 Jun 2017 C1 U1 non-standard Yes Details →
2.3.0 31 May 2016 C1 U1 non-standard Yes Details →
2.2.0 12 Apr 2016 C1 U1 non-standard Yes Details →
2.1.0 12 Apr 2016 C1 U1 non-standard Yes Details →
2.0.0 10 Apr 2016 C1 U1 non-standard Yes Details →
1.2.1 03 Feb 2016 C1 U1 non-standard Yes Details →
1.2.0 02 Feb 2016 C1 U1 non-standard Yes Details →
1.1.0 27 Dec 2015 C1 U1 non-standard Yes Details →
1.0.0 21 Dec 2015 C1 U1 non-standard Yes Details →
0.96.0 19 Dec 2015 C1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 lektor

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-28335: Lektor Database Path Traversal Vulnerability 9.1 critical 3.3.11 27 Mar 2024
Lektor Package - Path Traversal Vulnerability N/A unrated 3.3.11 27 Mar 2024

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 lektor

Is lektor safe to use?

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

Vulert scores lektor 77/100, which reads as in good shape. 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 lektor affected?

No. 3.3.14, 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 lektor should I use?

3.3.14 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 lektor have?

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

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

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