Local data corruption by low-privileged users
Published Feb 10, 2026 · Updated Feb 10, 2026
Improper conditions checking in Intel NPU Driver for Windows before 32.0.100.4297 allows local users to corrupt data. Intel identifies the affected locus only as firmware within Ring 3 user applications and has not published the failed condition or input. Exploitation requires a low-privileged authenticated user, local access, no user interaction, and additional attack requirements; the documented direct impact is limited to low-integrity data corruption.
Summary
What happened
Improper conditions checking in Intel NPU Driver for Windows before 32.0.100.4297 allows local users to corrupt data. Intel identifies the affected locus only as firmware within Ring 3 user applications and has not published the failed condition or input. Exploitation requires a low-privileged authenticated user, local access, no user interaction, and additional attack requirements; the documented direct impact is limited to low-integrity data corruption.
The record
- CVE
- CVE-2025-33030
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel NPU Driver
- Classifications
- CWE-754, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See references
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo