Cyber Resilience

CVE-2025-59257

Microsoft Windows 11 24H2 ≤ 10.0.26100.6899

Published
14 October 2025
Modified
20 October 2025
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.014 70th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2025-59257 is a medium-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Microsoft Windows 11 24H2. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

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

EU & UK References

Vulnerability Data

Improper validation of specified type of input in Windows Local Session Manager (LSM) allows an authorized attacker to deny service over a network.

CWE(s)
CWE-1287

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
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.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-25179Same product: Microsoft Windows 11 24H2
CVE-2025-59259Same product: Microsoft Windows 11 24H2
CVE-2025-58729Same product: Microsoft Windows 11 24H2
CVE-2025-55701Same product: Microsoft Windows 11 24H2
CVE-2025-59278Same product: Microsoft Windows 11 24H2
CVE-2025-59277Same product: Microsoft Windows 11 24H2
CVE-2024-49093Same product: Microsoft Windows 11 24H2
CVE-2026-26115Same vendor: Microsoft
CVE-2024-43625Same product: Microsoft Windows 11 24H2
CVE-2024-43642Same product: Microsoft Windows 11 24H2

Affected Assets

microsoft
windows 11 24h2
≤ 10.0.26100.6899
microsoft
windows 11 25h2
≤ 10.0.26200.6899
microsoft
windows server 2022 23h2
≤ 10.0.25398.1913
microsoft
windows server 2025
≤ 10.0.26100.6899

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.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input type validation during development.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type-validation flaws but does not prevent them during development.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and type checking to prevent improper type handling.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly include validation of input data types and formats.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote defensive input handling and type enforcement at system boundaries.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper type validation of all external inputs.

References