dbcve.org
Cumulus LinuxOperating system · Nvidia

CVE-2025-33181

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 inject a 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

Command injection vulnerability in the NVUE interface of NVIDIA Cumulus Linux and NVOS allows a low-privileged user to inject arbitrary shell commands, potentially leading to privilege escalation from unprivileged to administrative access.

MitigationRestrict NVUE interface access to trusted, minimally-privileged users; monitor for suspicious command activity; apply vendor patches when released; implement network segmentation to limit exposure.

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. Check Cumulus Linux version
    Run `cat /etc/cumulus/linux-version` or `cat /etc/os-release` to obtain the installed Cumulus Linux version
    Affected if The version is < 5.14.0, OR >= 5.9.0 and < 5.9.4, OR >= 5.11.0 and < 5.11.4
  2. Check NVOS version
    Run `nv show version` or `nvosctl show version` (or check system documentation for version command) to obtain the installed NVOS version
    Affected if The version is < 25.02.2452, OR < 25.02.4282, OR < 25.02.5030
  3. Verify NVUE interface is accessible
    Confirm the NVUE CLI/API is enabled and reachable by attempting `nv` command or checking `/etc/nvue` configuration directory exists and service status
    Affected if NVUE interface is enabled and running on the system
  4. Identify low-privileged NVUE users
    Run `nv get system user` or check `/etc/nvue/users.conf` to enumerate users with NVUE access and their privilege levels
    Affected if Any non-administrator user accounts exist with NVUE interface access

You are affected if your Cumulus Linux or NVOS version falls within the affected ranges AND the NVUE interface is 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

Restrict NVUE interface access to trusted, minimally-privileged users; monitor for suspicious command activity; apply vendor patches when released; implement network segmentation to limit exposure.

Recommended fix High confidence

Cumulus Linux: 5.14.0 (or 5.9.4+, 5.11.4+); NVOS: 25.02.2452 / 25.02.4282 / 25.02.5030 (depending on release train)

  1. 1. Identify the currently installed Cumulus Linux or NVOS version using 'nv show version' or 'cat /etc/os-release'
  2. 2. For Cumulus Linux: If running < 5.9.0, upgrade to 5.9.4 or later; if running >= 5.9.0 and < 5.11.0, upgrade to 5.9.4 or later; if running >= 5.11.0 and < 5.14.0, upgrade to 5.11.4 or later; if running >= 5.14.0, you are not affected
  3. 3. For NVOS: Identify the specific release train (25.02.xxxx) and upgrade to the corresponding fixed version: 25.02.2452, 25.02.4282, or 25.02.5030 depending on your branch
  4. 4. Schedule a maintenance window as upgrades may require system reboot
  5. 5. Backup current NVUE configuration using 'nv config save' before upgrade
  6. 6. Perform the upgrade via the vendor's recommended upgrade procedure (apt-get update && apt-get upgrade for Cumulus Linux, or vendor-provided mechanism for NVOS)
  7. 7. After upgrade, verify the version is now >= the fixed release and confirm NVUE functionality
Caveat Upgrade may require reboot; review release notes for any configuration changes between versions

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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