CVE-2026-47573 in Windowsinfo

Summary

by MITRE • 09/30/2026

NVIDIA NVAPI for Windows contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 09/30/2026

The identified security flaw resides within the NVIDIA NVAPI library for Windows environments, specifically manifesting as a memory corruption issue classified under CWE-787: Out-of-bounds Write. This vulnerability arises from improper validation or handling of input parameters during API calls, allowing an attacker to write data beyond the boundaries of allocated memory buffers. Such out-of-bounds writes are particularly dangerous because they can overwrite adjacent memory structures, including control flow data such as return addresses on the stack or function pointers in heap metadata. The presence of this flaw indicates a failure in boundary checking mechanisms within the NVAPI implementation, which is commonly used by applications to interact with NVIDIA graphics processing units and related hardware features.

From an operational perspective, the exploitation of this vulnerability can lead to severe consequences ranging from denial of service to arbitrary code execution. When memory boundaries are violated, the immediate effect may be application instability or crashes, resulting in a denial of service for users relying on GPU-accelerated applications. However, more critically, skilled attackers can leverage precise out-of-bounds writes to manipulate program control flow. By overwriting critical data structures, an attacker can redirect execution to malicious shellcode injected into the process memory space. This capability aligns with ATT&CK technique T1059: Command and Scripting Interpreter if used for initial access or lateral movement, and potentially T1203: Exploitation for Client Execution if targeting end-user systems directly through compromised applications that utilize NVAPI.

The impact extends beyond simple execution of code; successful exploitation can facilitate privilege escalation and information disclosure. If the vulnerable application runs with elevated privileges, such as system-level services or administrative tools interacting with GPU drivers, an attacker could gain higher-level access to the operating system. This aligns with ATT&CK technique T1068: Exploitation for Privilege Escalation. Furthermore, memory corruption can allow attackers to read sensitive data stored in adjacent memory regions, leading to information disclosure of credentials or proprietary algorithms protected by the application. Data tampering is also a significant risk, as overwritten memory may include configuration settings or user data, compromising integrity and trustworthiness of the system state.

Mitigation strategies must focus on both immediate remediation and long-term defensive measures. The primary action is to apply vendor-provided patches that address the specific buffer handling logic within NVAPI. Organizations should prioritize updating NVIDIA drivers and associated software components to versions where this vulnerability has been resolved. In addition to patching, implementing strict application whitelisting can prevent unauthorized or unpatched applications from executing code that might trigger the exploit. Network segmentation and monitoring for anomalous memory access patterns using endpoint detection and response solutions can also help detect exploitation attempts in real-time. Security teams should review their inventory of systems utilizing NVIDIA hardware and ensure compliance with current security baselines to minimize exposure to this class of memory corruption vulnerabilities.

Responsible

Nvidia

Reservation

05/19/2026

Disclosure

09/30/2026

Moderation

accepted

EPSS

0.00000

KEV

no

Activities

low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!