High Injection

CVE-2025-33228 — OS Command Injection in NVIDIA Cuda Toolkit

NVIDIA Nsight Systems contains a vulnerability in the gfx_hotspot recipe, where an attacker could cause an OS command injection by supplying a malicious string to the process_nsys_rep_cli.py script if the script is invoked manually. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, and information disclosure.

Published Jan 20, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: nvidia

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 1.4% (30-day exploitation probability)+11
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

1.39%

ahead of 72% of scored CVEs · Oct 14, 2026

Affects

NVIDIA

Cuda Toolkit

CVSS base

7.3

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — nvidia.custhelp.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (NVIDIA Cuda Toolkit).
Apply the fixed version or the patch documented under Remediation.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
NVIDIA	Cuda Toolkit	< 13.1.0	Vulnerable	NIST National Vulnerability Database
NVIDIA	Cuda Toolkit	version All versions prior to CUDA Toolkit 13.1	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.3	CVSS 3.1	High	1.3	5.9	psirt@nvidia.com via NIST National Vulnerability Database
7.3	CVSS 3.1	High	—	—	nvidia via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H (score shown at the top: psirt@nvidia.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.39%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Look for parameters with command/query metacharacters and unexpected child processes of the service.

endpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · nvidia/cuda toolkit
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 7.3
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jan 20, 2026 · nvidia

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

nvidia.custhelp.com/app/answers/detail/a_id/5755
Patch, Vendor Advisory, NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2025-33228
US Government Resource, VDB Entry, NIST National Vulnerability Database
www.cve.org/CVERecord
Third Party Advisory, NIST National Vulnerability Database

Elsewhere on this site

NVIDIA
every CVE for this vendor

Injection
same class

CWE-78
other pages naming this weakness

Related CVEs (same products)

High CVE-2025-33229 Uncontrolled Search Path Element in NVIDIA Cuda Toolkit Jan 20, 2026
High CVE-2025-33230 OS Command Injection in NVIDIA Cuda Toolkit Jan 20, 2026
Medium CVE-2025-33231 Uncontrolled Search Path Element in NVIDIA Cuda Toolkit Jan 20, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-33228 is "OS Command Injection in NVIDIA Cuda Toolkit", rated High. It affects Cuda Toolkit (NVIDIA); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.3 describes technical severity. EPSS 1.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.