Act nowDisclosed

Advisory · CVE-2026-97815

Heap overflow in Windows Error Reporting allows network code execution

Windows Error Reporting has a heap-based buffer overflow an unauthenticated attacker can trigger over the network to execute code. Microsoft rates it CVSS 3.1 9.8.

Advisory published October 13, 2026Independent summary
Vendor
Microsoft
Product
Windows Error Reporting
Identifier / CWE
CVE-2026-97815
CWE-122
Action timing
Immediate
ELI5

Explain it like I’m five

Even the component that phones home about crashes can be crashed into running someone else's code.

SIMPLIFIED_ATTACK_PATH03 STEPS
  1. 01Reach the component

    An unauthenticated attacker sends crafted network traffic to a Windows system running Windows Error Reporting.

  2. 02Memory flaw triggers

    The component mishandles the input and corrupts or reuses memory outside its intended bounds.

  3. 03Code runs

    The attacker gains code execution in the component's context on the target system.

What happened

Microsoft disclosed CVE-2026-97815 in its October 2026 update guide: a heap-based buffer overflow (CWE-122) in Windows Error Reporting lets an unauthorized attacker execute code over a network.

Microsoft lists the affected Windows releases in its update guide. Apply the October 2026 security updates for your release rather than relying on a version guess here.

What to do

  1. Inventory every Windows Error Reporting deployment, including test, training, and individually managed instances.
  2. Apply the vendor fix or upgrade exactly as directed in the linked vendor bulletin or advisory.
  3. Restrict network access to Windows Error Reporting while remediation is underway, especially for internet-facing instances.
  4. Review application and server logs for error reporting service crashes and gaps in crash telemetry from affected hosts.
  5. Check for accounts, content, or configuration created outside normal change processes, and rotate exposed credentials where access cannot be ruled out.
  6. Verify the deployed version or patch level after remediation.

Management note

Error Reporting runs everywhere and is rarely watched. Fold it into the fleet-wide October patch and check for telemetry gaps.