CVE-2025-33229
Nvidia Cuda Toolkit ≤ 13.1.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-33229 is a high-severity Uncontrolled Search Path Element (CWE-427) vulnerability in Nvidia Cuda Toolkit. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-33229 is a vulnerability in NVIDIA Nsight Visual Studio for Windows, specifically within the Nsight Monitor component. It enables an attacker to execute arbitrary code with the same privileges as the NVIDIA Nsight Visual Studio Edition Monitor application. Successful exploitation may result in escalation of privileges, code execution, data tampering, denial of service, and information disclosure. The issue carries a CVSS v3.1 base score of 7.3 (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) and is linked to CWE-427: Untrusted Search Path. It was published on 2026-01-20.
The vulnerability requires local access (AV:L), low attack complexity (AC:L), low privileges (PR:L), and user interaction (UI:R) for exploitation, with no change in scope (S:U). A low-privileged local attacker could leverage this to achieve high-impact confidentiality, integrity, and availability effects by executing code under the privileges of the affected Nsight Monitor process.
Mitigation guidance is available in official advisories, including the NVIDIA security bulletin at https://nvidia.custhelp.com/app/answers/detail/a_id/5755, the NVD detail page at https://nvd.nist.gov/vuln/detail/CVE-2025-33229, and the CVE record at https://www.cve.org/CVERecord?id=CVE-2025-33229.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3373
Vulnerability Data
NVIDIA Nsight Visual Studio for Windows contains a vulnerability in Nsight Monitor where an attacker can execute arbitrary code with the same privileges as the NVIDIA Nsight Visual Studio Edition Monitor application. A successful exploit of this vulnerability may lead…
more
to escalation of privileges, code execution, data tampering, denial of service, and information disclosure.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Establishes restrictive configuration settings that can define and lock down approved search paths.
Enforces approved authorizations so that only intended actors can place or modify elements in the search path.
Limits privileges so unintended actors cannot write to or control directories in the product's search path.
Restricts logical and physical access to change system configuration, including search-path settings and directories.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly address design of search paths and resource loading.
Hardened configuration baselines can enforce safe search-path settings and reduce exposure.
Execution allow-listing can block malicious binaries placed in hijackable search locations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uncontrolled search-path issues but does not prevent them by itself.
Restricting software installation reduces the chance that an attacker-controlled path element is introduced into the search path.
Secure system architecture and engineering principles require explicit control over search paths and resource locations.
Secure coding practices directly address the use of fixed or controlled search paths that can be influenced by unintended actors.
Configuration management can enforce approved search-path settings but does not inherently prevent the weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-427