Skip to main content

System Information Console EUVDEUVD-2026-99870

| CVE-2026-70157 CRITICAL
Heap-based Buffer Overflow (CWE-122)
2026-10-13 secure@microsoft.com GHSA-83r3-p4g7-wq7q
9.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Windows System Information Console over network
  2. Delivery
    Send crafted oversized input
  3. Exploit
    Overflow heap buffer (CWE-122)
  4. Execution
    Corrupt memory structures
  5. Persist
    Execute arbitrary code
  6. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the Windows System Information Console component and, per CVSS AV:N/AC:L/PR:N/UI:N, requires no authentication, no user interaction, and only network reachability to the vulnerable component. The practical limiting factor is network exposure of that console/service: hosts where the affected component is not network-accessible (e.g. blocked by host or perimeter firewall) are not reachable by a remote attacker. All supported Windows client and server builds below the patched versions listed in EUVD (e.g. Windows 11 24H2 <10.0.26100.9711, Server 2025 <10.0.26100.33650, Server 2016 <10.0.14393.9612) are affected until the vendor update is applied.

Impact

Signals diverge in an informative way. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N) describes a maximally dangerous flaw: remote, network-reachable, no authentication, no user interaction, with total confidentiality/integrity/availability impact (C:H/I:H/A:H) - consistent with a heap-based buffer overflow (CWE-122) yielding remote code execution. CISA SSVC reinforces the ceiling with Automatable:yes and Technical Impact:total, meaning that once an exploit exists it could be reliably scaled. However, SSVC Exploitation is explicitly 'none', there is NO CISA KEV listing, NO public POC reported in the provided data, and NO EPSS probability was supplied, so near-term real-world exploitation is currently UNPROVEN despite the perfect-storm CVSS vector. The practical takeaway: this is a genuine high-priority patch-now item because the product (Windows) is ubiquitous, a vendor patch already exists, and the flaw is automatable with total impact - but it is NOT yet an emergency driven by observed in-the-wild activity. Treat it as a high-value target that will likely attract exploit development rather than something confirmed to be under attack today. Missing EPSS and the absence of any technical exploitation detail in the single MSRC reference are the main gaps; weaponization difficulty of the heap overflow cannot be judged from the data provided.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends specially crafted data to a vulnerable Windows System Information Console component reachable over the network, triggering a heap-based buffer overflow that corrupts memory and allows arbitrary code execution in the context of the affected process. No user interaction or credentials are required per the CVSS vector. No public exploit identified at time of analysis, so this reflects the theoretical attack path rather than an observed campaign.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 1.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Unauthenticated remote code execution is possible against the Windows System Information Console, where a heap-based buffer overflow (CWE-122) reachable over the network lets an attacker with no credentials and no user interaction run arbitrary code in the context of the affected component. Every supported Windows client and server build remains vulnerable until the vendor's security updates are applied - for example Windows 11 24H2 build 10.0.26100.9711, Windows Server 2025 build 10.0.26100.33650, and Windows Server 2016 build 10.0.14393.9612. Exploitation has not been observed (CISA SSVC exploitation: none) and no public exploit code is identified at time of analysis, but with CVSS 9.8, an automatable attack path, and total technical impact, the divergence between the severity signal and the quiet exploitation picture is the central risk consideration - the practical constraint is simply whether the affected component is network-reachable on a given host.

RemediationAI

Vendor-released patch: apply the Microsoft security update for CVE-2026-70157 so each host moves to or above its fixed build - Windows 11 24H2 10.0.26100.9711, Windows 11 23H2 10.0.22631.7652, Windows 11 25H2 10.0.26200.9711, Windows 11 26H1 10.0.28000.3231, Windows 11 26H2 10.0.26300.9711, Windows 10 21H2/22H2 10.0.19044.7807, Windows 10 1607 and Server 2016 10.0.14393.9612, Windows 10 1809 and Server 2019 10.0.17763.9376, Server 2022 10.0.20348.5761, Server 2025 10.0.26100.33650, Server 2012 R2 6.3.9600.23470, and Server 2012 6.2.9200.26434 - using the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70157 as the authoritative source and prioritising internet-facing servers and any host where the console component is remotely reachable. Because the assessed vector is AV:N/PR:N/UI:N, the only real precondition for exploitation is network reachability, so until patching completes treat host and perimeter firewall rules as the primary compensating control: block inbound access to the port or service backing the System Information Console from untrusted networks, and remove any NAT/port-forward exposure of it, accepting the trade-off that legitimate remote management or monitoring integrations against that component will break and will need an out-of-band or VPN-only path instead. Where the component is not required at all, disable it and restrict the endpoint to loopback or authenticated administrative channels; additionally segment server VLANs so a single reachable host cannot be used as a pivot, and note that reducing the attack surface this way only buys time - it does not remove the memory-corruption defect, so the update remains mandatory. Detection should focus on unexpected process crashes of the console component and on anomalous outbound network behaviour from hosts running it, and enterprises should verify build numbers post-patching rather than relying on update-success telemetry alone.

Affected VersionsENISA

Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 20 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-122, heap-based buffer overflow: data is written past the end of a heap-allocated buffer inside the Windows System Information Console, corrupting adjacent heap metadata and adjoining structures so that an attacker who controls the overflowing input can influence program state and redirect execution. Because the overflow is heap-based rather than stack-based, exploitation typically requires heap grooming to place attacker-influenced data where an overwritten pointer, vtable, or length field will be used, but the payoff is the same - code execution within the privileges of the affected process. The CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H describes the worst case cleanly: the component is reachable over the network, no authentication (PR:N) and no user interaction (UI:N) are required, attack complexity is low, scope remains unchanged (the compromise stays inside the vulnerable component's security context), and confidentiality, integrity, and availability are all fully lost. No CPE strings were supplied with this record, so the EUVD build numbers below serve as the authoritative product/version identifiers; the affected component is part of the Windows operating system itself, which is why the affected list spans nearly the entire modern Windows client and server estate rather than a single SKU.

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

Vendor (microsoft) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 9.8 CRITICAL

Description states unauthorized network code execution, so AV:N/PR:N/UI:N/AC:L; heap overflow RCE yields full C:H/I:H/A:H with unchanged scope.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:19 cve.org
CRITICAL 9.8

DescriptionCVE.org

Heap-based buffer overflow in Windows System Information Console allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

A critical heap-based buffer overflow in the Windows System Information Console enables remote code execution across all supported Windows client and server builds, potentially allowing an attacker to take full control of affected systems. While no public exploit has been identified at the time of analysis, the broad deployment of Windows and the high severity rating mean that unpatched environments remain at significant risk of operational disruption or data compromise. Leadership should treat this as a priority patching effort to protect organizational assets and maintain business continuity.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
1.0%
Top 39% exploitable
Prevalence
Ubiquitous
Microsoft Windows client and server, present in most enterprise environments
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 1.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

55
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy