Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local access
-
ExploitTarget Windows Error Reporting auth weakness
-
ExecutionElevate to SYSTEM/high privilege
-
ImpactFull host compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Strong authentication
|
| Exploitation Conditions | Requires the attacker to already have authenticated local access to the Windows host with at least low-level privileges (PR:L), per the CVSS vector - this is a local elevation-of-privilege flaw in the Windows Error Reporting component, not a remote entry point. No user interaction is needed (UI:N) and attack complexity is low (AC:L), so exploitation is reliable once a foothold exists. The primary limiting factor is that remote-only or unauthenticated attackers cannot exploit it directly; it must be chained after initial access. Affected systems are those running pre-patch builds listed in the EUVD data (e.g., Windows 11 24H2 below 10.0.26100.9711, Windows Server 2025 below 10.0.26100.33650, Windows 10 22H2 below 10.0.19044.7807); patched builds are not vulnerable. |
| Impact | This is a credible, patch-now local privilege escalation rather than a hype-driven high-CVSS item. The CVSS 3.1 base of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) describes a low-complexity local attack requiring only low existing privileges and no user interaction, yielding total compromise (C/I/A all High) of the host. The CISA SSVC framework corroborates severity on impact (Technical Impact: total) but materially lowers urgency: Exploitation is rated 'none' (no observed active exploitation) and Automatable is 'no' (consistent with a local-only vector that cannot be worm-like mass-exploited). No KEV listing, no POC, and no EPSS score were provided in the input, so there is no evidence of in-the-wild or public exploit activity at this time. The signals are consistent rather than conflicting: high technical impact but local-only reach and no exploitation evidence. The practical priority is driven by the ubiquity of Windows and the fact that PR:L means any low-privileged user or foothold can attempt escalation; this is a standard 'second-stage' EoP that attackers chain after initial access, so it should be patched promptly even without exploitation evidence. One minor data caveat: the input Tags label this 'Information Disclosure', which conflicts with the description and CWE-1390 (Weak Authentication) elevation-of-privilege framing - treat it as an EoP. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged foothold on a Windows host (e.g., a standard user account or a compromised low-integrity process) abuses the weak authentication in the Windows Error Reporting component to run code at a higher privilege level. Because the vector is local with low complexity and no user interaction, exploitation is straightforward once local access exists, though it requires that pre-existing foothold. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in the Windows Error Reporting (WER) component of supported Windows 10, Windows 11, and Windows Server builds allows an attacker who already holds low-level authenticated local access to elevate to a more privileged context on the same host. The flaw is a weak-authentication defect (CWE-1390) in WER that is locally exploitable with low complexity, no user interaction, and no special preconditions beyond an existing foothold, which is what drives the 7.8 base score. Microsoft has published a fix through its regular update channel (MSRC update guide), and at time of analysis there is no public exploit identified and CISA SSVC records exploitation as none, so this is a patch-now hardening item rather than an urgent emergency-mitigation case.
RemediationAI
Apply the Microsoft security update listed in the MSRC update guide for CVE-2026-83840 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83840); the EUVD data defines the fixed builds as Windows 11 26H1 10.0.28000.3231, 26H2 10.0.26300.9711, 25H2 10.0.26200.9711, 24H2 10.0.26100.9711, and 23H2 10.0.22631.7652; Windows 10 22H2 and 21H2 10.0.19044.7807, 1809 10.0.17763.9376, and 1607 10.0.14393.9612; and Windows Server 2025 10.0.26100.33650, Server 2022 10.0.20348.5761, Server 2019 10.0.17763.9376, and Server 2016 10.0.14393.9612 - Windows 11 24H2 and Windows Server 2025 share the 10.0.26100.x branch, so confirm the deployed build number rather than the marketing release name. Patch availability is confirmed by the vendor, so the primary action is deploying these cumulative updates through Windows Update, WSUS, or your patch-management pipeline, prioritizing servers and any hosts where non-administrative users have interactive or RDP access. Because exploitation requires an existing low-privileged local foothold, the effective compensating controls are reducing that surface rather than disabling WER outright: restrict interactive and RDP logon rights to staff who genuinely need them, remove local administrator rights from standard users, and segment hosts so an initial compromise cannot easily be chained into privilege escalation - the trade-off is operational friction and help-desk load, since users lose the ability to self-install software or run elevated troubleshooting. Disabling the Windows Error Reporting service (WerSvc) is technically possible but is not recommended as a mitigation: it suppresses crash diagnostics and telemetry used for incident response, is unsupported by Microsoft, and does not remove the underlying weak-authentication code path if the component is invoked by another privileged caller, so it should only be considered as a short-term measure on isolated, high-value servers until the update can be applied. Given the SSVC assessment of Exploitation: none, there is no evidence of active exploitation and no public exploit code identified at time of analysis, so normal patch-cycle urgency is appropriate, with faster tracking for internet-exposed or multi-user systems where a local foothold is most likely to be obtained.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 16 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Error Reporting is the built-in crash and telemetry subsystem (WerSvc and related broker infrastructure) that captures fault data, writes dumps, and brokers reports to Microsoft; because it operates across user and system contexts it is a classic local privilege-escalation target when its authentication or impersonation checks are too permissive. CVE-2026-83840 is classified as CWE-1390, Weak Authentication, meaning WER does not adequately verify the identity or privilege level of the caller before performing a privileged operation, letting an attacker with only low privileges have that operation executed in WER's higher-privileged context. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H confirms the mechanics: a local attack path (AV:L), no user interaction (UI:N), low complexity (AC:L), and a prerequisite of low-level authenticated access (PR:L), with high confidentiality, integrity, and availability impact but scope unchanged (S:U) since the compromise stays within the same Windows security boundary. The EUVD version data maps the exposure precisely to the WER binaries shipped in the listed Windows servicing branches, so the risk is concentrated on unpatched endpoints and servers rather than on any third-party or networked service.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only EoP requiring a low-privileged foothold (AV:L, PR:L), no user interaction and low complexity, resulting in full host compromise (C/I/A High), same-scope.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Weak authentication in Windows Error Reporting allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A weakness in the Windows Error Reporting component that ships with supported Windows 10, Windows 11, and Windows Server builds would allow someone who already holds a foothold on a machine to escalate to a higher-privileged context on that same host. Because it cannot be reached remotely, the realistic exposure is concentrated in environments where attackers or untrusted users already operate on endpoints, making this primarily a post-compromise stepping stone toward lateral movement rather than a direct entry point. Microsoft has released a fix and no public exploit has been observed, so this should be managed as a scheduled hardening obligation rather than an emergency.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2026-100011
GHSA-88vf-hx2m-4qqf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB