dbcve.org
NvflareApplication · Nvidia

CVE-2026-24178

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 2.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NVIDIA NVFlare Dashboard contains a vulnerability in the user management and authentication system where an unauthenticated attacker may cause authorization bypass through user-controlled key. A successful exploit of this vulnerability may lead to privilege escalation, data tampering, information disclosure, code execution, and denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA NVFlare Dashboard contains an authorization bypass vulnerability in its user management and authentication system. The flaw allows unauthenticated attackers to bypass authentication controls through user-controlled keys, potentially gaining administrative access to the platform.

MitigationApply the NVIDIA security patch immediately upon release. Until then, restrict network access to the Dashboard to trusted networks only and monitor for unauthorized access attempts. Review and rotate any exposed or configurable keys.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NvflareApplication
Affected:< 2.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if NVIDIA NVFlare is installed
    Check for NVFlare installation by looking for the 'nvflare' package or installation directory. Common locations: pip list | grep nvflare, or check /opt/nvflare, ~/nvflare, or the working directory where it was installed.
    Affected if NVFlare is present on the system and the version is below 2.7.2
  2. Determine installed NVFlare version
    Run 'nvflare --version' or 'pip show nvflare' to retrieve the exact installed version number.
    Affected if The installed version is lower than 2.7.2 (e.g., 2.7.1, 2.7.0, 2.6.x, etc.)
  3. Verify if Dashboard component is enabled
    Check if the NVFlare Dashboard is running or configured. Look for dashboard-related configuration files (e.g., startup/ folder, project.yml, or dashboard.py process). Inspect running processes for dashboard ports or services.
    Affected if The Dashboard component is running or configured and the version is vulnerable
  4. Inspect user-controlled authentication keys
    Examine NVFlare configuration for any configurable keys related to authentication, authorization, or user management. Check files like project.yml, admin authentication config, or any custom key configurations in the startup directory.
    Affected if User-controlled or configurable authentication keys are present in the configuration

A system is affected if NVIDIA NVFlare with Dashboard is installed at a version below 2.7.2 and the Dashboard is accessible or configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.2 or later
Fixed in 2.7.2
Interim mitigation

Apply the NVIDIA security patch immediately upon release. Until then, restrict network access to the Dashboard to trusted networks only and monitor for unauthorized access attempts. Review and rotate any exposed or configurable keys.

Recommended fix High confidence

NVFlare 2.7.2 or latest stable release

  1. 1. Back up your current NVFlare configuration and any custom settings
  2. 2. Download NVFlare version 2.7.2 or the latest stable release from the official NVIDIA repository
  3. 3. Stop the NVFlare Dashboard service if it is currently running
  4. 4. Install the upgraded NVFlare package using standard installation procedures (e.g., pip install nvflare==2.7.2 or equivalent for your deployment method)
  5. 5. Restore your configuration from the backup if needed
  6. 6. Restart the NVFlare Dashboard service
  7. 7. Verify the upgrade was successful and the Dashboard is functioning correctly
  8. 8. Test that the authorization bypass vulnerability is no longer present by confirming user management controls work as expected
Caveat Review release notes for any configuration or API changes between your current version and 2.7.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nvflare Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24178 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data