Cyber & AI intelligence
Wasteland.
Briefs indexed2597
Issues28
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-69493 2026-09-08

CVE-2026-69493: Critical Unauthenticated RCE in Windows Event Logging Service

"Microsoft disclosed an out-of-bounds read in the Windows Event Logging Service that allows an unauthorized attacker to execute code over a network, rated CVSS 9.8 (Critical)."

Microsoft disclosed an out-of-bounds read in the Windows Event Logging Service that allows an unauthorized attacker to execute code over a network, rated CVSS 9.8 (Critical).

What Is It

CVE-2026-69493 is an out-of-bounds read in the Windows Event Logging Service. Per Microsoft's description, the flaw "allows an unauthorized attacker to execute code over a network." The CVE was published on 2026-09-08 by Microsoft ([email protected]) and currently carries an NVD status of "Awaiting Analysis."

The Microsoft-assigned CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, scoring 9.8 / Critical.

Why It Matters

The vector describes the worst realistic combination for a Windows service bug: network-reachable, low attack complexity, no privileges required, and no user interaction, with high impact to confidentiality, integrity, and availability. That means an attacker who can reach the affected service over the network needs no credentials and no help from a user to reach code execution.

The affected component is also notable. Event Logging is a core Windows service that is generally present and running by default on typical client and server installations, so exposure is unlikely to be limited to an optional role or add-on product. Hardened or heavily customized builds may differ, and administrators should confirm service state in their own environments.

CVE-2026-69493 does not currently appear in CISA's Known Exploited Vulnerabilities catalog, so active exploitation is not confirmed at this time.

What's Vulnerable

Microsoft lists the following affected products, fixed at the builds shown:

One caveat on the build list: Windows Server 2025 and Windows 11 24H2 share the 26100 build base and servicing branch, yet the advisory data shows two very different revision numbers for them (10.0.26100.33438 and 10.0.26100.9445). Both values are reproduced here as published, but administrators validating patch level on 26100-based systems should confirm the applicable revision directly against the MSRC entry for their specific product before treating a machine as fixed.

Coverage spans 32-bit, x64, and ARM64 platforms depending on the release.

Patch Status

Microsoft has published fixed build numbers for each affected release listed in the advisory, which indicates updates are available for those products. Patch to at or above the listed build for each product. No CISA KEV due date or additional required action applies to this CVE at present.

Sources