VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

chainlit: vulnerability history, versions and safety

chainlit is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 119 releases, from Jan 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C2 H2 L1 U6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
11 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all chainlit vulnerabilities

Vulert verdict on chainlit 2.12.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 2.12.0 — unaffected i
  • Vulnerabilities on record 11 over 1 year · 11 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 41 packages i
  • Stars 12,517 i
  • Last release 1 month ago i
  • Licence Apache-2.0 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 chainlit, 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.12.0 25 Aug 2026 none Apache-2.0 — Details →
2.11.1 22 Apr 2026 C1 H1 U2 Apache-2.0 Yes Details →
2.11.0 07 Apr 2026 C1 H1 U2 Apache-2.0 Yes Details →
2.10.1 27 Mar 2026 C1 H1 U2 Apache-2.0 Yes Details →
2.10.0 05 Mar 2026 C2 H1 U3 Apache-2.0 Yes Details →
2.9.6 20 Jan 2026 C2 H1 U3 Apache-2.0 Yes Details →
2.9.5 12 Jan 2026 C2 H1 U3 Apache-2.0 Yes Details →
2.9.4 25 Dec 2025 C2 H1 U3 Apache-2.0 Yes Details →
2.9.3 04 Dec 2025 C2 H2 U5 Apache-2.0 Yes Details →
2.9.2 22 Nov 2025 C2 H2 U5 Apache-2.0 Yes Details →
2.9.1 20 Nov 2025 C2 H2 U5 Apache-2.0 Yes Details →
2.9.0 08 Nov 2025 C2 H2 U5 Apache-2.0 Yes Details →
2.8.5 07 Nov 2025 C2 H2 U5 Apache-2.0 Yes Details →
2.8.4 29 Oct 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.8.3 06 Oct 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.8.2 01 Oct 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.8.1 24 Sep 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.8.0 13 Sep 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.7.2 26 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.7.1.1 21 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.7.1 21 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.7.0 21 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.9 14 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.8 08 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.7 07 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.6 05 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.5 03 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.4 01 Aug 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.3 25 Jul 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.2 16 Jul 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.1 16 Jul 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.6.0 01 Jul 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.5.5 14 Apr 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.400 29 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.302 26 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.301 24 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.3 23 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.201 20 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.2 19 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.1 13 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.0 12 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.4.0rc0 09 Mar 2025 C2 H2 L1 U6 Apache-2.0 Yes Details →
2.3.0 09 Mar 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.2.1 15 Feb 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.2.0 08 Feb 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.1.2 05 Feb 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.1.1 03 Feb 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.1.0 30 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.603 28 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.602 27 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.601 25 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.6 24 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.5 21 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.4 17 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.3 14 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.2 10 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.1 09 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.0 06 Jan 2025 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.0rc1 19 Dec 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.0rc0 08 Nov 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.3.2 08 Nov 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.0.dev2 25 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.3.1 25 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.3.0 22 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.0.dev1 22 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
2.0.0.dev0 08 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.3.0rc1 04 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.3.0rc0 02 Oct 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.2.0rc0 18 Sep 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.2.0 16 Sep 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.404 04 Sep 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.403rc0 13 Aug 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.402 07 Aug 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.401 02 Aug 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.400 29 Jul 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.400rc1 15 Jul 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.400rc0 12 Jul 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.306 03 Jul 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.305 26 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.304 21 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.303 20 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.302 18 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.301 14 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300 13 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300rc5 11 Jun 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300rc4 30 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300rc3 30 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300rc2 29 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300rc1 28 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.300rc0 27 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.202 22 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.201 21 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.200 21 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.101 14 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.0 13 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.0rc1 06 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.1.0rc0 06 May 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.0.506 30 Apr 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.0.505 23 Apr 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.0.504 16 Apr 2024 C1 H1 L1 U4 Apache-2.0 Yes Details →
1.0.503 15 Apr 2024 C1 H1 L1 U4 — Yes Details →
1.0.502 08 Apr 2024 C1 H1 L1 U4 — Yes Details →
1.0.501 08 Apr 2024 C1 H1 L1 U4 — Yes Details →
1.0.500 02 Apr 2024 C1 H1 L1 U4 — Yes Details →
1.0.401 11 Mar 2024 C1 H1 L1 U4 — Yes Details →
1.0.400 06 Mar 2024 C1 H1 L1 U4 — Yes Details →
1.0.301 20 Feb 2024 C1 H1 L1 U4 — Yes Details →
1.0.300 20 Feb 2024 C1 H1 L1 U4 — Yes Details →
1.0.200 22 Jan 2024 C1 H1 L1 U4 — Yes Details →
1.0.101 12 Jan 2024 C1 H1 L1 U4 — Yes Details →
1.0.100 10 Jan 2024 C1 H1 L1 U4 — Yes Details →
1.0.0 08 Jan 2024 C1 H1 L1 U4 — Yes Details →
1.0.0rc3 21 Dec 2023 C1 H1 L1 U4 — Yes Details →
1.0.0rc2 18 Dec 2023 C1 H1 L1 U4 — Yes Details →
1.0.0rc1 13 Dec 2023 C1 H1 L1 U4 — Yes Details →
1.0.0rc0 12 Dec 2023 C1 H1 L1 U4 — Yes Details →
0.7.700 28 Nov 2023 C1 H1 L1 U4 — Yes Details →
0.7.604 21 Nov 2023 C1 H1 L1 U4 — Yes Details →
0.7.604rc2 17 Nov 2023 C1 H1 L1 U4 — Yes Details →
0.7.604rc1 17 Nov 2023 C1 H1 L1 U4 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 11

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

03 Vulnerabilities

Recorded vulnerabilities for chainlit

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-45018: Chainlit Command Injection Vulnerability Leading to Remote Code Execution 9.8 critical 2.12.0 25 Aug 2026
CVE-2026-45018: Chainlit Command Injection Vulnerability Leading to Remote Code Execution 9.8 critical 2.12.0 10 Sep 2026
CVE-2026-22219: Chainlit Server-Side Request Forgery (SSRF) Vulnerability 8.3 high 2.9.4 20 Jan 2026
CVE-2026-22219: Chainlit Server-Side Request Forgery (SSRF) Vulnerability 7.7 high 2.9.4 07 Jul 2026
CVE-2026-56104: Chainlit Session Hijacking Vulnerability 7.4 critical 2.10.1 22 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 chainlit

Is chainlit safe to use?

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

Vulert scores chainlit 64/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 chainlit affected?

No. 2.12.0, 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 chainlit should I use?

2.12.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 chainlit have?

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

11 vulnerabilities were recorded for chainlit in the last 12 months, and the oldest entry in this database dates to 14 Jan 2026. 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 chainlit 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 chainlit for upcoming vulnerabilities?

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