CVE-2025-20622VulnerabilityPublished 11 Nov 2025Updated 12 Nov 2025

CVE-2025-20622: Intel(R) NPU Drivers for Windows · Information Disclosure

Affects Intel(R) NPU Drivers for WindowsSource CVE Database V5

Not known to be exploited · CVSS 2.0 Low : upgrade to 32.0.100.4023 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 32.0.100.4023

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Intel(R) NPU Drivers for Windows to 32.0.100.4023.

Affected software

Product	Affected	Fixed in
Intel(R) NPU Drivers for Windows	Affected <32.0.100.4023	Fixed in 32.0.100.4023

AI-suggested

1. Immediately update Intel NPU drivers to version 32.0.100.4023 or later to ensure the vulnerability is patched. 2. Implement strict local access controls to limit authenticated user access to trusted personnel only, reducing the risk of insider threats exploiting the vulnerability. 3. Employ endpoint detection and response (EDR) solutions to monitor for unusual local activity that could indicate attempts to exploit memory disclosure. 4. Conduct regular audits of user privileges and remove unnecessary local accounts or restrict their permissions to minimize the attack surface. 5. Use application whitelisting to prevent unauthorized software from running locally, which could attempt to exploit the vulnerability. 6. Educate users about the importance of safeguarding their credentials and the risks of local exploitation. 7. For highly sensitive environments, consider isolating systems with Intel NPUs or limiting their use to reduce exposure. 8. Maintain up-to-date inventory of hardware and drivers to quickly identify and remediate vulnerable systems. 9. 10. Integrate vulnerability management processes to ensure timely patch deployment and verification.

Description

Sensitive information uncleared in resource before release for reuse for some Intel(R) NPU Drivers for Windows before version 32.0.100.4023 within Ring 3: User Applications may allow an information disclosure. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable data exposure. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Impact

For European organizations, the primary impact of CVE-2025-20622 is the potential exposure of sensitive information residing in memory buffers managed by Intel NPU drivers. Although the confidentiality impact is rated low, any leakage of sensitive data could have compliance implications under regulations such as GDPR, especially if personal or proprietary information is involved. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, organizations with high-value AI workloads or sensitive data processed via Intel NPU-enabled systems should consider the risk more seriously. The requirement for local authenticated access limits the attack surface to insiders or compromised user accounts, emphasizing the importance of strong endpoint security and access controls. Since the vulnerability is in a driver component, it may affect a range of Windows-based devices including desktops, laptops, and servers that utilize Intel NPUs. The absence of known exploits reduces immediate threat but does not eliminate future risk, particularly as attackers may develop techniques to leverage this flaw. Overall, the impact is moderate for organizations with relevant hardware and sensitive data, and low for others.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01304.html (opens in a new tab)

Community reviews

Loading reviews…