VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nebari: vulnerability history, versions and safety

nebari is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 79 releases, first recorded in May 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 M1 U1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 nebari vulnerabilities

Vulert verdict on nebari 2025.10.1 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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 2025.10.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 06 May 2024 i
  • Highest CVSS 4.8 i
  • With no published fix 1 i
  • Depended on by 9 packages i
  • Stars 328 i
  • Last release 11 months ago i
  • Licence BSD-3-Clause 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 nebari, 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
2026.3.1rc2 19 May 2026 M1 BSD-3-Clause No Details →
2026.3.1rc1 10 Mar 2026 M1 BSD-3-Clause No Details →
2025.10.1 04 Nov 2025 M1 BSD-3-Clause No Details →
2025.10.1rc2 30 Oct 2025 M1 BSD-3-Clause No Details →
2025.10.1rc1 23 Oct 2025 M1 BSD-3-Clause No Details →
2025.6.1 06 Jun 2025 M1 BSD-3-Clause No Details →
2025.6.1rc1 05 Jun 2025 M1 BSD-3-Clause No Details →
2025.4.2 25 Apr 2025 M1 BSD-3-Clause No Details →
2025.4.2rc1 25 Apr 2025 M1 BSD-3-Clause No Details →
2025.4.1 11 Apr 2025 M1 BSD-3-Clause No Details →
2025.4.1rc1 08 Apr 2025 M1 BSD-3-Clause No Details →
2025.3.1 17 Mar 2025 M1 BSD-3-Clause No Details →
2025.3.1rc1 12 Mar 2025 M1 BSD-3-Clause No Details →
2025.2.1 20 Feb 2025 M1 BSD-3-Clause No Details →
2025.2.1rc2 13 Feb 2025 M1 BSD-3-Clause No Details →
2025.2.1rc1 07 Feb 2025 M1 BSD-3-Clause No Details →
2025.1.1rc1 27 Jan 2025 M1 BSD-3-Clause No Details →
2024.12.1 13 Dec 2024 M1 BSD-3-Clause No Details →
2024.12.1rc1 10 Dec 2024 M1 BSD-3-Clause No Details →
2024.11.1 21 Nov 2024 M1 BSD-3-Clause No Details →
2024.11.1rc3 18 Nov 2024 M1 BSD-3-Clause No Details →
2024.11.1rc2 13 Nov 2024 M1 BSD-3-Clause No Details →
2024.11.1rc1 05 Nov 2024 M1 BSD-3-Clause No Details →
2024.9.1 27 Sep 2024 M1 BSD-3-Clause No Details →
2024.9.1rc4 27 Sep 2024 M1 BSD-3-Clause No Details →
2024.9.1rc3 23 Sep 2024 M1 BSD-3-Clause No Details →
2024.9.1rc2 19 Sep 2024 M1 BSD-3-Clause No Details →
2024.9.1rc1 17 Sep 2024 M1 BSD-3-Clause No Details →
2024.7.1 08 Aug 2024 M1 BSD-3-Clause No Details →
2024.7.1rc3 02 Aug 2024 M1 BSD-3-Clause No Details →
2024.7.1rc2 31 Jul 2024 M1 BSD-3-Clause No Details →
2024.7.1rc1 29 Jul 2024 M1 BSD-3-Clause No Details →
2024.6.1 26 Jun 2024 M1 BSD-3-Clause No Details →
2024.6.1rc4 26 Jun 2024 M1 BSD-3-Clause No Details →
2024.6.1rc3 05 Jun 2024 M1 BSD-3-Clause No Details →
2024.6.1rc2 28 May 2024 M1 BSD-3-Clause No Details →
2024.6.1rc1 23 May 2024 U1 BSD-3-Clause Yes Details →
2024.5.1 13 May 2024 U1 BSD-3-Clause Yes Details →
2024.5.1rc1 06 May 2024 U1 BSD-3-Clause Yes Details →
2024.4.1 20 Apr 2024 M1 U1 BSD-3-Clause No Details →
2024.4.1rc1 16 Apr 2024 M1 U1 BSD-3-Clause No Details →
2024.3.3 27 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.3.3rc1 25 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.3.2 14 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.3.2rc1 14 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.3.1 11 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.3.1rc2 08 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.3.1rc1 05 Mar 2024 M1 U1 BSD-3-Clause No Details →
2024.1.1 30 Jan 2024 M1 U1 BSD-3-Clause No Details →
2024.1.1rc5 20 Jan 2024 M1 U1 BSD-3-Clause No Details →
2024.1.1rc4 19 Jan 2024 M1 U1 BSD-3-Clause No Details →
2024.1.1rc3 18 Jan 2024 M1 U1 BSD-3-Clause No Details →
2024.1.1rc2 11 Jan 2024 M1 U1 BSD-3-Clause No Details →
2024.1.1rc1 10 Jan 2024 M1 U1 BSD-3-Clause No Details →
2023.12.1 22 Dec 2023 M1 U1 BSD-3-Clause No Details →
2023.12.1rc1 21 Dec 2023 M1 U1 BSD-3-Clause No Details →
2023.11.1 15 Nov 2023 M1 U1 BSD-3-Clause No Details →
2023.11.1rc1 14 Nov 2023 M1 U1 BSD-3-Clause No Details →
2023.10.1 21 Oct 2023 M1 U1 BSD-3-Clause No Details →
2023.10.1rc1 20 Oct 2023 M1 U1 BSD-3-Clause No Details →
2023.9.1rc1 28 Sep 2023 M1 U1 BSD-3-Clause No Details →
2023.7.2 04 Aug 2023 M1 U1 BSD-3-Clause No Details →
2023.7.2rc1 03 Aug 2023 M1 U1 BSD-3-Clause No Details →
2023.7.1 22 Jul 2023 M1 U1 BSD-3-Clause No Details →
2023.7.1rc1 21 Jul 2023 M1 U1 BSD-3-Clause No Details →
2023.5.1 05 May 2023 M1 U1 BSD-3-Clause No Details →
2023.5.1rc1 05 May 2023 M1 U1 BSD-3-Clause No Details →
2023.4.1 12 Apr 2023 M1 U1 BSD-3-Clause No Details →
2023.4.1a5 10 Apr 2023 M1 U1 BSD-3-Clause No Details →
2023.4.1a4 06 Apr 2023 M1 U1 BSD-3-Clause No Details →
2023.1.1 01 Feb 2023 M1 U1 BSD-3-Clause No Details →
2023.1.1rc1 28 Jan 2023 M1 U1 BSD-3-Clause No Details →
2022.11.1 01 Dec 2022 M1 U1 BSD-3-Clause No Details →
2022.11.1rc4 01 Dec 2022 M1 U1 BSD-3-Clause No Details →
2022.11.1rc1 30 Nov 2022 M1 U1 BSD-3-Clause No Details →
2022.10.1 31 Oct 2022 M1 U1 BSD-3-Clause No Details →
2022.10.1rc2 27 Oct 2022 M1 U1 BSD-3-Clause No Details →
2022.10.1rc1 27 Oct 2022 M1 U1 BSD-3-Clause No Details →
0.0.1 25 Jan 2022 M1 U1 — No Details →

All 79 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 nebari

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-34529: Nebari prints temporary Keycloak root password 4.8 medium No fix published 06 May 2024
CVE-2024-34529: Nebari Exposes Temporary Keycloak Root Password N/A unrated 2024.6.1rc2 06 May 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 nebari

Is nebari safe to use?

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

What is nebari's Vulert package health score?

Vulert scores nebari 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 nebari affected?

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

Which version of nebari should I use?

2025.10.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 nebari have?

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

0 vulnerabilities were recorded for nebari 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 nebari 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 nebari for upcoming vulnerabilities?

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