{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-33229 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-33229 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-33229 is a high-severity code injection vulnerability in NVIDIA CUDA Toolkit, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-33229 and fix it if it is affected.\n\nWhat it is: CVE-2025-33229 is a high-severity code injection vulnerability in NVIDIA CUDA Toolkit, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-33229 in the wild and no public exploit code.\n\nAffected product: NVIDIA CUDA Toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-33229/ (Markdown: https://insights.sbomify.com/CVE-2025-33229/index.md)","id":"CVE-2025-33229","markdown":"https://insights.sbomify.com/CVE-2025-33229/index.md","name":"CVE-2025-33229","record":{"aliases":["DEBIAN-CVE-2025-33229","GHSA-65x9-9gp9-wcq3","UBUNTU-CVE-2025-33229"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Nsight Visual Studio Edition","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code and escalate privileges via the NVIDIA Nsight Monitor application in Visual Studio.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"cuda_toolkit","vendor":"nvidia"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"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 to escalation of privileges, code execution, data tampering, denial of service, and information disclosure.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in CUDA Toolkit","id":"CVE-2025-33229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33230"},"packages":[],"prev":{"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33228"},"products":["CUDA Toolkit"],"published":"2026-01-20","related":[{"cvss_score":7.8,"headline":"Integer overflow in NVIDIA CUDA Toolkit","id":"CVE-2022-21821","kev_date_added":null,"published":"2022-03-29"},{"cvss_score":7.8,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2020-5991","kev_date_added":null,"published":"2020-10-30"},{"cvss_score":7.3,"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33228","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":7.3,"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33230","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":6.7,"headline":"Other in CUDA Toolkit","id":"CVE-2025-33231","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":5.3,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2023-25512","kev_date_added":null,"published":"2023-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["NVIDIA"]},"summary":"An attacker can execute arbitrary code and escalate privileges via the NVIDIA Nsight Monitor application in Visual Studio.","url":"https://insights.sbomify.com/CVE-2025-33229/"}