Windows Kernel-Mode Drivers Information Disclosure Vulnerability
Why It Matters
Analysis dossierWhy It Matters
Incorrect authorization in Windows Kernel-Mode Drivers allows an authorized attacker to disclose information locally.
Review
No
Unknown
Risk basis: Microsoft or Microsoft-managed product relevance
Affected Products & Remediation
10 source-backed products- Windows Server 2025 (Server Core installation) · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 25H2 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 25H2 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 24H2 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 24H2 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows Server 2025 · version range not provided by source · Microsoft MSRC · Source
- Windows 11 version 26H1 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 26H1 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 26H2 for ARM64-based Systems · version range not provided by source · Microsoft MSRC · Source
- Windows 11 Version 26H2 for x64-based Systems · version range not provided by source · Microsoft MSRC · Source
Vendor or catalog guidance (source)
- Microsoft MSRC: Install the security update KB5126646 listed by MSRC
- Microsoft MSRC: Install the security update KB5127648 listed by MSRC
- Microsoft MSRC: Install the security update KB5127646 listed by MSRC
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Unknown
- Exploited (source statement)
- No
- Publicly disclosed (source)
- Unknown
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched microsoft-enterprise (Affected product: Windows Server 2025 (Server Core installation), Vendor: Microsoft); authorization-bypass (CWE-863)
Exposure
- Identify affected Microsoft products and compare local builds with the MSRC advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · The MSRC product/build mapping establishes applicability. · Rule microsoft-enterprise
- Locate affected authorization controls and verify deployed versions.Telemetry: Application inventory · The source must identify the affected control. · Rule authorization-bypass
Exploitation evidence
- Review the advisory's documented behavior on matching hosts before selecting a hunt.Telemetry: DeviceProcessEvents · Product family alone does not justify a CVE-specific detection. · Rule microsoft-enterprise
Show more (2)
Exploitation evidence
- Review privileged operations performed by unexpected users on affected deployments.Telemetry: Application audit logs · Authorization anomalies can support a targeted hunt. · Rule authorization-bypass
Response
- Confirm the source-stated KB or mitigation on matching assets.Telemetry: DeviceTvmSoftwareVulnerabilities · A post-update inventory check verifies remediation. · Rule microsoft-enterprise
CISA KEV Record
CISA KEV status was not determined for this record.
Change History & Source Data
— No recorded material change
- CNA / source
- secure@microsoft.com
- Record status · verification
- UPDATED · Unknown
- CPE
- Unknown
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-69971"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc