Vulnerability Database · PyPI · Package report

nicegui: vulnerability history, versions and safety

nicegui is a package in the PyPI ecosystem. Vulert records 34 vulnerabilities for it across 111 releases, from Apr 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
34 vulnerabilities recorded H7 M10 U17
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
31 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.

Vulert verdict on nicegui 3.18.0 i

Updated on 22 Oct 2026

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

Package health score 65/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.18.0 — unaffected i
  • Vulnerabilities on record 34 over 2 years · 31 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 264 packages i
  • Stars 16,295 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 nicegui, 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.18.0 07 Oct 2026 none MIT — Details →
3.17.1 18 Sep 2026 none MIT — Details →
3.17.0 16 Sep 2026 none MIT — Details →
3.16.0 12 Aug 2026 none MIT — Details →
3.15.0 23 Jul 2026 none MIT — Details →
3.14.0 30 Jun 2026 none MIT — Details →
3.13.0 09 Jun 2026 none MIT — Details →
3.12.1 21 May 2026 none MIT — Details →
3.12.0 12 May 2026 none MIT — Details →
3.11.1 25 Apr 2026 H1 M1 U2 MIT Yes Details →
3.11.0 24 Apr 2026 H1 M1 U2 MIT Yes Details →
3.10.0 07 Apr 2026 H1 M1 U2 MIT Yes Details →
3.9.0 19 Mar 2026 H1 M2 U3 MIT Yes Details →
3.8.0 24 Feb 2026 H1 M3 U4 MIT Yes Details →
3.7.1 05 Feb 2026 H2 M3 U5 MIT Yes Details →
3.7.0 05 Feb 2026 H2 M3 U5 MIT Yes Details →
3.6.1 21 Jan 2026 H3 M4 U7 MIT Yes Details →
3.6.0 21 Jan 2026 H3 M4 U7 MIT Yes Details →
3.5.0 08 Jan 2026 H3 M4 U7 MIT Yes Details →
3.4.1 16 Dec 2025 H4 M7 U11 MIT Yes Details →
3.4.0 08 Dec 2025 H4 M7 U11 MIT Yes Details →
3.3.1 17 Nov 2025 H5 M9 U14 MIT Yes Details →
3.3.0 13 Nov 2025 H5 M9 U14 MIT Yes Details →
3.2.0 28 Oct 2025 H5 M9 U14 MIT Yes Details →
3.1.0 22 Oct 2025 H5 M9 U14 MIT Yes Details →
3.0.4 10 Oct 2025 H5 M9 U14 MIT Yes Details →
3.0.3 06 Oct 2025 H5 M9 U14 MIT Yes Details →
3.0.2 04 Oct 2025 H5 M9 U14 MIT Yes Details →
3.0.1 04 Oct 2025 H5 M9 U14 MIT Yes Details →
3.0.0 03 Oct 2025 H5 M9 U14 MIT Yes Details →
2.24.2 23 Sep 2025 H5 M10 U15 MIT Yes Details →
2.24.1 11 Sep 2025 H5 M10 U15 MIT Yes Details →
3.0.0rc1 05 Sep 2025 H5 M10 U15 MIT Yes Details →
2.24.0 05 Sep 2025 H5 M10 U15 MIT Yes Details →
2.23.3 26 Aug 2025 H5 M10 U15 MIT Yes Details →
2.23.2 25 Aug 2025 H5 M10 U15 MIT Yes Details →
2.23.1 25 Aug 2025 H5 M10 U15 MIT Yes Details →
2.23.0 21 Aug 2025 H5 M10 U15 MIT Yes Details →
2.22.2 09 Aug 2025 H5 M10 U15 MIT Yes Details →
2.22.1 01 Aug 2025 H5 M10 U15 MIT Yes Details →
2.22.0 31 Jul 2025 H5 M10 U15 MIT Yes Details →
2.21.1 10 Jul 2025 H4 M9 U13 MIT Yes Details →
2.21.0 08 Jul 2025 H4 M9 U13 MIT Yes Details →
2.20.0 13 Jun 2025 H4 M9 U13 MIT Yes Details →
2.19.0 02 Jun 2025 H4 M9 U13 MIT Yes Details →
2.18.0 23 May 2025 H4 M9 U13 MIT Yes Details →
2.17.0 12 May 2025 H4 M9 U13 MIT Yes Details →
2.16.1 05 May 2025 H4 M9 U13 MIT Yes Details →
2.16.0 02 May 2025 H4 M9 U13 MIT Yes Details →
2.15.0 16 Apr 2025 H4 M9 U13 MIT Yes Details →
2.14.1 09 Apr 2025 H4 M9 U13 MIT Yes Details →
2.14.0 08 Apr 2025 H4 M9 U13 MIT Yes Details →
2.13.0 18 Mar 2025 H4 M9 U13 MIT Yes Details →
2.12.1 04 Mar 2025 H4 M8 U12 MIT Yes Details →
2.12.0 03 Mar 2025 H4 M8 U12 MIT Yes Details →
2.11.1 11 Feb 2025 H4 M8 U12 MIT Yes Details →
2.11.0 04 Feb 2025 H4 M8 U12 MIT Yes Details →
2.10.1 21 Jan 2025 H4 M8 U12 MIT Yes Details →
2.10.0 20 Jan 2025 H4 M8 U12 MIT Yes Details →
2.9.1 06 Jan 2025 H4 M7 U11 MIT Yes Details →
2.9.0 19 Dec 2024 H5 M7 U12 MIT Yes Details →
2.8.1 06 Dec 2024 H5 M7 U12 MIT Yes Details →
2.8.0 05 Dec 2024 H5 M7 U12 MIT Yes Details →
2.7.0 22 Nov 2024 H5 M7 U12 MIT Yes Details →
2.5.0 25 Oct 2024 H5 M7 U12 MIT Yes Details →
2.4.0 16 Oct 2024 H5 M7 U12 MIT Yes Details →
2.3.0 04 Oct 2024 H5 M7 U12 MIT Yes Details →
2.2.0 27 Sep 2024 H5 M7 U12 MIT Yes Details →
2.1.0 06 Sep 2024 H5 M7 U12 MIT Yes Details →
2.0.1 31 Aug 2024 H5 M7 U12 MIT Yes Details →
2.0.0 31 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.37 29 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.36 22 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.35 15 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.34 05 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.33 05 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.31 05 Aug 2024 H5 M7 U12 MIT Yes Details →
1.4.30 26 Jul 2024 H5 M7 U12 MIT Yes Details →
1.4.29 09 Jul 2024 H5 M7 U12 MIT Yes Details →
1.4.28 28 Jun 2024 H5 M7 U12 MIT Yes Details →
1.4.27 13 Jun 2024 H5 M7 U12 MIT Yes Details →
1.4.26 27 May 2024 H5 M7 U12 MIT Yes Details →
1.4.25 13 May 2024 H5 M7 U12 MIT Yes Details →
1.4.24 06 May 2024 H5 M7 U12 MIT Yes Details →
1.4.23 25 Apr 2024 H5 M7 U12 MIT Yes Details →
1.4.22 15 Apr 2024 H5 M7 U12 MIT Yes Details →
1.4.21 12 Apr 2024 H5 M7 U12 MIT Yes Details →
1.4.20 04 Apr 2024 H6 M7 U13 MIT Yes Details →
1.4.19 22 Mar 2024 H6 M7 U13 MIT Yes Details →
1.4.18 07 Mar 2024 H6 M7 U13 MIT Yes Details →
1.4.17 27 Feb 2024 H6 M7 U13 MIT Yes Details →
1.4.16 26 Feb 2024 H6 M7 U13 MIT Yes Details →
1.4.15 09 Feb 2024 H6 M7 U13 MIT Yes Details →
1.4.14 05 Feb 2024 H6 M7 U13 MIT Yes Details →
1.4.13 29 Jan 2024 H6 M7 U13 MIT Yes Details →
1.4.12 22 Jan 2024 H6 M7 U13 MIT Yes Details →
1.4.11 15 Jan 2024 H6 M7 U13 MIT Yes Details →
1.4.10 13 Jan 2024 H6 M7 U13 MIT Yes Details →
1.4.9 05 Jan 2024 H6 M7 U13 MIT Yes Details →
1.4.8 27 Dec 2023 H6 M7 U13 MIT Yes Details →
1.4.7 26 Dec 2023 H6 M7 U13 — Yes Details →
1.4.6 18 Dec 2023 H6 M7 U13 — Yes Details →
1.4.5 04 Dec 2023 H5 M7 U12 — Yes Details →
1.4.4 04 Dec 2023 H5 M7 U12 — Yes Details →
1.4.3 22 Nov 2023 H5 M7 U12 — Yes Details →
1.4.2 06 Nov 2023 H5 M7 U12 — Yes Details →
1.4.1 26 Oct 2023 H5 M7 U12 — Yes Details →
1.4.0 23 Oct 2023 H5 M7 U12 — Yes Details →
1.3.18 20 Oct 2023 H5 M7 U12 — Yes Details →
1.3.17 16 Oct 2023 H5 M7 U12 — Yes Details →
1.3.16 06 Oct 2023 H5 M7 U12 — Yes Details →
1.3.15 26 Sep 2023 H5 M7 U12 — Yes Details →
1.3.14 19 Sep 2023 H5 M7 U12 — Yes Details →
1.3.13 29 Aug 2023 H5 M7 U12 — Yes Details →
1.3.12 25 Aug 2023 H5 M7 U12 — Yes Details →
1.3.11 18 Aug 2023 H5 M7 U12 — Yes Details →
1.3.10 18 Aug 2023 H5 M7 U12 — Yes Details →
1.3.9 10 Aug 2023 H5 M7 U12 — Yes Details →
1.3.8 07 Aug 2023 H5 M7 U12 — Yes Details →
1.3.7 03 Aug 2023 H5 M7 U12 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 5
  • 2026 28

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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 nicegui

Is nicegui safe to use?

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

Vulert scores nicegui 65/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 nicegui affected?

No. 3.18.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 nicegui should I use?

3.18.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 nicegui have?

34 vulnerabilities are recorded for nicegui in the PyPI ecosystem: 0 critical, 7 high, 10 medium and 0 low, plus 17 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 nicegui vulnerabilities disclosed?

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

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