PatchSiren cyber security CVE debrief
CVE-2026-50367 Microsoft CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-14T18:17:37.363Z and has not been modified since then. The NVD entry is currently Analyzed. This vulnerability, CVE-2026-50367, involves an incorrect access of an indexable resource leading to a 'range error' in the Windows Sensor Data Service, allowing an authorized attacker to elevate privileges locally. The issue has a CVSS score of 7.8, classified as HIGH severity, affecting multiple versions of Windows 10, Windows 11, and Windows Server, including versions 2019, 2022, and 2025. System administrators and security teams should prioritize patching for high-risk systems due to the local elevation of privileges nature of the issue. The CVE and NVD provide information on the vulnerability's existence and affected systems, but specific details about exploitation or additional impacts are not provided. Further investigation and monitoring are recommended. The official CVE record and NVD details offer insights into the vulnerability and its impact.
- Vendor
- Microsoft
- Product
- Windows 10 Version 1809
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-14
- Original CVE updated
- 2026-07-22
- Advisory published
- 2026-07-14
- Advisory updated
- 2026-07-22
Who should care
System administrators and security teams responsible for Windows systems, particularly those using Windows 10, Windows 11, and Windows Server versions, should be aware of this vulnerability. Given the local elevation of privileges nature of the issue, prioritizing patching for high-risk systems is crucial.
Technical summary
The vulnerability, CVE-2026-50367, is caused by an incorrect access of an indexable resource, leading to a 'range error' in the Windows Sensor Data Service. This allows an authorized attacker to elevate their privileges locally. The issue has a CVSS score of 7.8 and is classified as HIGH severity. It affects multiple versions of Windows 10, Windows 11, and Windows Server, including versions 2019, 2022, and 2025.
Defensive priority
High priority should be given to patching this vulnerability due to its potential for local privilege escalation. Systems at higher risk, such as those exposed to untrusted users or with high-value assets, should be prioritized for patching.
Recommended defensive actions
- Apply the official patch from Microsoft as soon as possible.
- Conduct an inventory of affected systems and prioritize patching based on risk.
- Implement compensating controls such as enhanced monitoring and access restrictions.
- Verify the effectiveness of patches through testing and validation.
- Consider temporary mitigations if patching cannot be immediately applied.
Evidence notes
The CVE record and NVD details provide information on the vulnerability's existence and affected systems. However, specific details about exploitation or additional impacts are not provided in the source corpus. Further investigation and monitoring are recommended.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-50367 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-50367
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-50367 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-50367
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50367
[email protected] - Patch, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.