VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

litestar: vulnerability history, versions and safety

litestar is a package in the PyPI ecosystem. Vulert records 18 vulnerabilities for it across 66 releases, from May 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded H6 M3 L1 U8
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
12 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all litestar vulnerabilities

Vulert verdict on litestar 2.25.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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 2.25.0 — affected i
  • Vulnerabilities on record 18 over 2 years · 12 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 8.3 i
  • With no published fix 1 i
  • Depended on by 180 packages i
  • Stars 8,515 i
  • Last release this month 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 litestar, 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.25.0 18 Oct 2026 H1 U1 MIT No Details →
2.24.0 11 Jun 2026 H1 U1 MIT No Details →
2.23.0 29 May 2026 H1 U1 MIT No Details →
2.22.0 20 May 2026 H1 U1 MIT No Details →
2.21.1 07 Mar 2026 H1 M1 U2 MIT Yes Details →
2.21.0 14 Feb 2026 H1 M1 U2 MIT Yes Details →
2.20.0 08 Feb 2026 H1 M1 U2 MIT Yes Details →
2.19.0 14 Dec 2025 H2 M3 U5 MIT Yes Details →
2.18.0 05 Oct 2025 H1 M1 U5 MIT Yes Details →
2.17.0 10 Aug 2025 H2 M1 U6 MIT Yes Details →
2.16.0 04 May 2025 H1 M1 L1 U5 MIT Yes Details →
2.15.2 06 Apr 2025 H1 M1 L1 U5 MIT Yes Details →
2.15.1 27 Feb 2025 H1 M1 L1 U5 MIT Yes Details →
2.15.0 26 Feb 2025 H1 M1 L1 U5 MIT Yes Details →
2.14.0 08 Jan 2025 H1 M1 L1 U5 MIT Yes Details →
2.13.0 20 Nov 2024 H1 M1 L1 U5 MIT Yes Details →
2.12.1 21 Sep 2024 H2 M1 L1 U6 MIT Yes Details →
2.12.0 21 Sep 2024 H2 M1 L1 U6 MIT Yes Details →
2.11.0 27 Aug 2024 H2 M1 L1 U6 MIT Yes Details →
2.10.0 26 Jul 2024 H3 M1 L1 U6 MIT No Details →
2.9.1 21 Jun 2024 H3 M1 L1 U6 MIT No Details →
2.9.0 02 Jun 2024 H3 M1 L1 U6 MIT No Details →
2.6.4 06 May 2024 H3 M1 L1 U6 MIT No Details →
2.7.2 06 May 2024 H3 M1 L1 U6 MIT No Details →
2.8.3 06 May 2024 H3 M1 L1 U6 MIT No Details →
2.8.2 09 Apr 2024 H4 M1 L1 U7 MIT No Details →
2.8.1 08 Apr 2024 H4 M1 L1 U7 MIT No Details →
2.8.0 05 Apr 2024 H4 M1 L1 U7 MIT No Details →
2.7.1 27 Mar 2024 H3 M1 L1 U7 MIT No Details →
2.7.0 10 Mar 2024 H3 M1 L1 U7 MIT No Details →
2.6.3 04 Mar 2024 H3 M1 L1 U7 MIT No Details →
2.6.2 02 Mar 2024 H3 M1 L1 U7 MIT No Details →
2.6.1 14 Feb 2024 H3 M1 L1 U7 MIT No Details →
2.6.0 06 Feb 2024 H3 M1 L1 U7 MIT No Details →
2.5.5 04 Feb 2024 H3 M1 L1 U7 MIT No Details →
2.5.4 31 Jan 2024 H3 M1 L1 U7 MIT No Details →
2.5.3 29 Jan 2024 H3 M1 L1 U7 MIT No Details →
2.5.2 27 Jan 2024 H3 M1 L1 U7 MIT No Details →
2.5.1 18 Jan 2024 H3 M1 L1 U7 MIT No Details →
2.5.0 06 Jan 2024 H3 M1 L1 U7 MIT No Details →
2.4.5 23 Dec 2023 H3 M1 L1 U7 MIT No Details →
2.4.4 13 Dec 2023 H3 M1 L1 U7 MIT No Details →
2.4.3 07 Dec 2023 H3 M1 L1 U7 MIT No Details →
2.4.2 02 Dec 2023 H3 M1 L1 U7 MIT No Details →
2.4.1 28 Nov 2023 H3 M1 L1 U7 MIT No Details →
2.4.0 27 Nov 2023 H3 M1 L1 U7 MIT No Details →
2.3.2 06 Nov 2023 H3 M1 L1 U7 MIT No Details →
2.3.1 04 Nov 2023 H3 M1 L1 U7 MIT No Details →
2.3.0 02 Nov 2023 H3 M1 L1 U7 MIT No Details →
2.2.1 13 Oct 2023 H3 M1 L1 U7 MIT No Details →
2.2.0 12 Oct 2023 H3 M1 L1 U7 MIT No Details →
2.1.1 25 Sep 2023 H3 M1 L1 U7 MIT No Details →
2.1.0 25 Sep 2023 H3 M1 L1 U7 MIT No Details →
2.0.1 21 Aug 2023 H3 M1 L1 U7 MIT No Details →
2.0.0 21 Aug 2023 H3 M1 L1 U7 MIT No Details →
2.0.0rc1 05 Aug 2023 H3 M1 L1 U6 MIT No Details →
2.0.0b4 21 Jul 2023 H3 M1 L1 U6 MIT No Details →
2.0.0b3 20 Jul 2023 H3 M1 L1 U6 MIT No Details →
2.0.0b2 24 Jun 2023 H3 M1 L1 U6 MIT No Details →
2.0.0b1 16 Jun 2023 H3 M1 L1 U6 MIT No Details →
2.0.0a7 14 May 2023 H3 M1 L1 U6 MIT No Details →
2.0.0a6 09 May 2023 H3 M1 L1 U6 MIT No Details →
2.0.0a5 26 Apr 2023 H3 M1 L1 U6 MIT No Details →
2.0.0a4 11 Apr 2023 H3 M1 L1 U6 MIT No Details →
2.0.0a3 07 Apr 2023 H3 M1 L1 U6 MIT No Details →
1.0.0a0 01 Apr 2023 H3 M1 L1 U6 MIT No Details →

All 66 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 4
  • 2025 2
  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for litestar

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-42370: Litestar Environment Variable Injection in docs-preview.yml Workflow 8.3 high No fix published 09 Aug 2024
CVE-2024-32982: Path Traversal Vulnerability in LiteStar and Starlite 8.2 high 2.8.3 06 May 2024
CVE-2024-32982: Litestar Path Traversal Vulnerability in Static File Serving 8.2 high 2.6.4 13 Jul 2026
CVE-2026-48060: Litestar HTML Injection Vulnerability via CSRF Token 8.1 high 2.22.0 13 Jul 2026
CVE-2026-48060: Litestar HTML Injection Vulnerability via CSRF Token 8.1 high 2.22.0 10 Jun 2026

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 litestar

Is litestar safe to use?

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

What is litestar's Vulert package health score?

Vulert scores litestar 60/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 litestar affected?

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

How many vulnerabilities does litestar have?

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

12 vulnerabilities were recorded for litestar in the last 12 months, and the oldest entry in this database dates to 06 May 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 litestar 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 litestar for upcoming vulnerabilities?

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