Security Resilience

CVE-2026-62811

Memory Safety in Microsoft Windows 11 23H2 ≤ 10.0.22631.7517

Published
11 August 2026
Modified
13 August 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0033 27th percentile
Risk Priority 56 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-62811 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft Windows 11 23H2. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Heap-based buffer overflow in Windows HTTP.sys allows an authorized attacker to elevate privileges locally.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-47652Same product: Microsoft Windows 11 23H2
CVE-2026-72940Same product: Microsoft Windows 11 23H2
CVE-2026-61359Same product: Microsoft Windows 11 23H2
CVE-2026-65672Same product: Microsoft Windows 11 23H2
CVE-2026-62695Same product: Microsoft Windows 11 23H2
CVE-2026-70114Same product: Microsoft Windows 11 23H2
CVE-2026-83757Same product: Microsoft Windows 11 23H2
CVE-2026-96909Same product: Microsoft Windows 11 23H2
CVE-2026-83931Same product: Microsoft Windows 11 23H2
CVE-2026-97794Same product: Microsoft Windows 11 23H2

Affected Assets

microsoft
windows 11 23h2
≤ 10.0.22631.7517 · ≤ 10.0.22631.7517
microsoft
windows 11 24h2
≤ 10.0.26100.9106 · ≤ 10.0.26100.9106
microsoft
windows 11 25h2
≤ 10.0.26200.9106 · ≤ 10.0.26200.9106
microsoft
windows 11 26h1
≤ 10.0.28000.2704 · ≤ 10.0.28000.2704
microsoft
windows server 2022
≤ 10.0.20348.5440
microsoft
windows server 2025
≤ 10.0.26100.33222

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 full match
blocks

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
blocks

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
blocks

Timely patching removes known heap-overflow instances after they exist.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance can detect heap overflows before release.

prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

finds

A.8.8's reach is DISCLOSURE — it surfaces heap-based buffer overflows only where they appear as published CVEs in third-party components in the inventory. CWE-122 is overwhelmingly an implementation-phase defect in custom code, which A.8.8 does not read; the disclosed third-party share is a minority, matching the same logic that graded A.8.8 -> CWE-89 at `partial`.

References