CVE-2025-33180
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 · uneditedNVIDIA 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 confidenceNVIDIA Cumulus Linux and NVOS contain a command injection vulnerability in the NVUE interface where a low-privileged user can inject arbitrary commands through insufficient input sanitization. This allows an authenticated but low-privileged user to escalate privileges by executing commands with elevated permissions.
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< 5.14.0>= 5.9.0, < 5.9.4>= 5.11.0, < 5.11.4< 25.02.2452< 25.02.4282< 25.02.5030CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionRun 'nv show system' or check /etc/os-release to determine if the system is running Cumulus Linux or NVOS, then note the version numberAffected if The installed version falls within any of the affected ranges: Cumulus Linux < 5.14.0, >= 5.9.0 but < 5.9.4, >= 5.11.0 but < 5.11.4; NVOS < 25.02.2452, < 25.02.4282, or < 25.02.5030
-
Verify NVUE interface is enabledCheck if the NVUE service is active and accessible by running 'systemctl status nvued' or attempting to connect to the NVUE API on port 443Affected if NVUE interface is running and accessible to authenticated users
-
Check for low-privileged NVUE usersReview user accounts with NVUE access using 'nv show' commands or by checking /etc/nvue/users.conf if present, focusing on non-admin accountsAffected if Low-privileged users exist with NVUE interface authentication credentials
-
Audit NVUE command logsReview system logs and NVUE audit logs for suspicious commands, particularly those containing shell metacharacters like ; | & $ or unexpected command patternsAffected if Logs show commands executed by low-privileged users containing potential injection payloads or unusual command patterns
-
Monitor for privilege escalation attemptsCheck authentication logs and command history for evidence of commands run with elevated permissions by non-privileged NVUE usersAffected if Low-privileged users have executed commands with root or elevated permissions through NVUE
The environment is affected if the system runs a vulnerable Cumulus Linux or NVOS version AND has the NVUE interface enabled with low-privileged user accounts that could exploit the command injection flaw.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.9.45.11.45.14.0
Apply vendor-provided patches for Cumulus Linux and NVOS when available. Until patches are released, limit NVUE interface access to trusted users only and monitor for suspicious command activity.
Cumulus Linux: 5.14.0 or later (5.9.x branch: 5.9.4+, 5.11.x branch: 5.11.4+); NVOS: 25.02.2452+/25.02.4282+/25.02.5030+ depending on release train
- Identify the currently running Cumulus Linux or NVOS version using 'nv show version' or 'cat /etc/cumulus/etc/build.conf'
- For Cumulus Linux 5.9.x: Upgrade to version 5.9.4 or later
- For Cumulus Linux 5.11.x: Upgrade to version 5.11.4 or later
- For Cumulus Linux 5.12.x/5.13.x: Upgrade to version 5.14.0 or later
- For NVOS: Upgrade to 25.02.2452 or later, 25.02.4282 or later, or 25.02.5030 or later depending on your release train
- Follow standard NVIDIA upgrade procedures using 'apt-get update && apt-get upgrade' or the specific upgrade documentation for your platform
- After upgrade, verify the NVUE interface is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33180 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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