cve.bz

CVE-2025-33230 nvidia cuda toolkit: OS Command Injection

7.3 highEPSS 1.4%Fix available

High (7.3) in nvidia cuda toolkit. EPSS 1.4% estimated probability of exploitation activity in the next 30 days.

On this page
NVIDIA Nsight Systems for Linux contains a vulnerability in the .run installer, where an attacker could cause an OS command injection by supplying a malicious string to the installation path. A successful exploit of this vulnerability might lead to escalation of privileges, code execution, data tampering, denial of service, and information disclosure.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 73rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-01-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-33230 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-33230?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-33230?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-33230 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
nvidia:cuda_toolkitbefore 13.1.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13nvidia-cuda-toolkitno fix listedDEBIAN-CVE-2025-33230
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 5 morenvidia-cuda-toolkitno fix listedUBUNTU-CVE-2025-33230

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated Important as it impacts the NVIDIA Nsight Systems installer. An attacker could achieve OS command injection by providing a malicious installation path during the execution of the installer. This could lead to escalation of privileges and arbitrary code execution on affected systems running NVIDIA Nsight Systems.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10cuda-nsight-systems-13-0Fix deferred
Red Hat Enterprise Linux 10cuda-nsight-systems-13-1Fix deferred
Red Hat Enterprise Linux 10nsight-systems-2025.3.2Fix deferred
Red Hat Enterprise Linux 10nsight-systems-2025.5.2Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-33230.

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON