Kernel memory corruption via unsafe registry read
Published Jan 14, 2026 · Updated Jan 14, 2026
Out-of-bounds write in egwindrvx64.sys in InsydeH2O Tools allows local users to corrupt driver memory via a registry value. The driver uses RTL_QUERY_REGISTRY_DIRECT to place an attacker-influenced registry value directly into a destination buffer without a safe size boundary. A local low-privileged user-mode process must control the registry value; Insyde does not publish the specific post-corruption outcome.
Summary
What happened
Out-of-bounds write in egwindrvx64.sys in InsydeH2O Tools allows local users to corrupt driver memory via a registry value. The driver uses RTL_QUERY_REGISTRY_DIRECT to place an attacker-influenced registry value directly into a destination buffer without a safe size boundary. A local low-privileged user-mode process must control the registry value; Insyde does not publish the specific post-corruption outcome.
The record
- CVE
- CVE-2025-12053
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Insyde Software
- Product
- InsydeH2O Tools
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 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 in the Solution
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.
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