Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

Nebari prints temporary Keycloak root password

CVE-2024-34529GHSA-vjc4-3vgx-pq9h

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI nebari

    Affected
    <= 2024.4.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2024-34529: 0.35% estimated exploitation activity in the next 30 days; percentile 29.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Nebari through 2024.4.1 prints the temporary Keycloak root password.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-vjc4-3vgx-pq9h

  2. Revision 1 · created ·

    Published from osv record GHSA-vjc4-3vgx-pq9h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-34529

Advisory: Nebari prints temporary Keycloak root password
IDs: CVE-2024-34529, GHSA-vjc4-3vgx-pq9h
Record: https://patchnext.com/advisories/cve-2024-34529 (revision 2, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nebari: affected <= 2024.4.1

## Suggested inspection (read-only)
- `python -m pip show nebari`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nebari.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vjc4-3vgx-pq9h (OSV record GHSA-vjc4-3vgx-pq9h lists affected ranges: PyPI nebari >=0 <=2024.4.1)
- Verified: https://github.com/advisories/GHSA-vjc4-3vgx-pq9h (GitHub-reviewed advisory GHSA-vjc4-3vgx-pq9h lists affected ranges: PyPI nebari >=0 <=2024.4.1)

Commands are suggestions: review each one before running it.

Loading voting…