dbcve.org
Cumulus LinuxOperating system · Nvidia

CVE-2025-33179

HIGH · 8.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 5.9.4 / 5.11.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Cumulus Linux and NVOS products contain a vulnerability in the NVUE interface, where a low-privileged user could run an unauthorized command. A successful exploit of this vulnerability might lead to escalation of privileges.

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 Cumulus Linux and NVOS contain a privilege escalation vulnerability in the NVUE (NVIDIA User Experience) command-line interface. A low-privileged user can bypass authorization controls to execute unauthorized commands, potentially achieving administrator-level access on affected networking devices.

MitigationApply the vendor-supplied patch or upgrade to a fixed Cumulus Linux/NVOS version as specified in NVIDIA's security advisory. Prioritize patching in test environments before production deployment.

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
Cumulus LinuxOperating system
Affected:< 5.14.0>= 5.9.0, < 5.9.4>= 5.11.0, < 5.11.4
NvosOperating system
Affected:< 25.02.2452< 25.02.4282< 25.02.5030

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 the operating system and version
    Run 'cat /etc/os-release' or 'nv show system' to determine if the system is running Cumulus Linux or NVOS and obtain the exact version number
    Affected if The installed version falls within any of the affected ranges: Cumulus Linux < 5.14.0, 5.9.0 to < 5.9.4, or 5.11.0 to < 5.11.4; NVOS < 25.02.2452, < 25.02.4282, or < 25.02.5030
  2. Verify NVUE interface is accessible
    Check if NVUE service is enabled by running 'nv list' or checking for the presence of NVUE configuration at /etc/nvue/ or by attempting to access the NVUE command set
    Affected if NVUE is installed and accessible on the system, providing the attack surface for this vulnerability
  3. Confirm NVUE API endpoint availability
    Test NVUE API responsiveness by attempting to connect to localhost port 8741 or checking service status with 'systemctl status nvx' or equivalent service command
    Affected if The NVUE service is running and accepting connections, allowing the exploitation vector to function
  4. Identify user account privilege levels
    Review existing user accounts and their roles using 'nv show auth' or check /etc/nvue/ for user configuration files and role assignments
    Affected if Low-privileged or non-administrative user accounts exist on the system and have any NVUE access, as these are the users who could potentially exploit the privilege escalation

A system is affected if it runs a vulnerable version of Cumulus Linux or NVOS and has NVUE interface accessible to low-privileged users.

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 5.9.4 / 5.11.4 / 5.14.0 or later
Fixed in 5.9.45.11.45.14.0
Interim mitigation

Apply the vendor-supplied patch or upgrade to a fixed Cumulus Linux/NVOS version as specified in NVIDIA's security advisory. Prioritize patching in test environments before production deployment.

Recommended fix High confidence

Cumulus Linux >= 5.14.0 (or 5.9.4+, 5.11.4+); NVOS >= 25.02.2452 (or respective fixed version per train)

  1. 1. Identify current Cumulus Linux or NVOS version using 'nv show system' or 'nv get system version'
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Back up all NVUE configurations using 'nv config save' or the appropriate backup mechanism
  4. 4. For Cumulus Linux: Upgrade to version 5.14.0 or later (or 5.9.4+ / 5.11.4+ if staying on older branches)
  5. 5. For NVOS: Upgrade to version 25.02.2452 or later for the 25.02 train, or the respective fixed version for other affected trains
  6. 6. After upgrade, verify the NVUE interface is functional and test that low-privileged users can no longer execute unauthorized commands
  7. 7. Verify the system is running the patched version using 'nv show system'
Caveat Review NVIDIA release notes for the target version for any configuration or behavioral changes that may affect existing setups

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

Fix this in Cumulus Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33179 — 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-2025-33179 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