Cyber Resilience

CVE-2025-59278

Microsoft Windows Server 2008 r2

Published
14 October 2025
Modified
27 October 2025
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.0026 17th percentile
Risk Priority 56 floored blend · peak EPSS

Summary

CVE-2025-59278 is a high-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Microsoft Windows Server 2008. 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 17th 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 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 Authentication Methods allows an authorized attacker to elevate privileges locally.

CWE(s)

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.
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.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59277Same product: Microsoft Windows 10 1507
CVE-2025-58729Same product: Microsoft Windows 10 1507
CVE-2025-55701Same product: Microsoft Windows 10 1507
CVE-2025-59259Same product: Microsoft Windows 10 1507
CVE-2026-25179Same product: Microsoft Windows 10 1607
CVE-2025-59275Same product: Microsoft Windows 10 1507
CVE-2024-49138Same product: Microsoft Windows 10 1507
CVE-2024-49122Same product: Microsoft Windows 10 1507
CVE-2024-43627Same product: Microsoft Windows 10 1507
CVE-2024-49072Same product: Microsoft Windows 10 1507

Affected Assets

microsoft
windows 10 1507
≤ 10.0.10240.21161
microsoft
windows 10 1607
≤ 10.0.14393.8519
microsoft
windows 10 1809
≤ 10.0.17763.7919
microsoft
windows 10 21h2
≤ 10.0.19044.6456
microsoft
windows 10 22h2
≤ 10.0.19045.6456
microsoft
windows 11 22h2
≤ 10.0.22621.6060
microsoft
windows 11 23h2
≤ 10.0.22631.6060
microsoft
windows 11 24h2
≤ 10.0.26100.6899
microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
+5 more product configuration(s) — see NVD for full list

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 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.

finds

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

prevents

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

prevents

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

prevents

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

prevents

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

References