Cyber Resilience

CVE-2026-45602

Microsoft Windows 10 21H2 ≤ 10.0.19044.7417

Published
09 June 2026
Modified
20 July 2026
Patch / advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0037 29th percentile
Risk Priority 67 floored blend · peak EPSS

Summary

CVE-2026-45602 is a critical-severity Acceptance of Extraneous Untrusted Data With Trusted Data (CWE-349) vulnerability in Microsoft Windows 10 21H2. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 29th 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 AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

No cwe for this issue in Windows DHCP Server allows an unauthorized attacker to perform tampering over a network.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
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.
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-43636Same product: Microsoft Windows 10 1607
CVE-2024-49079Same product: Microsoft Windows 10 1607
CVE-2026-32162Same product: Microsoft Windows 10 1809
CVE-2024-43646Same product: Microsoft Windows 10 1607
CVE-2025-48804Same product: Microsoft Windows 10 1607
CVE-2024-49138Same product: Microsoft Windows 10 1607
CVE-2025-21240Same product: Microsoft Windows 10 1607
CVE-2025-21223Same product: Microsoft Windows 10 1607
CVE-2024-49122Same product: Microsoft Windows 10 1607
CVE-2024-43627Same product: Microsoft Windows 10 1607

Affected Assets

microsoft
windows 10 1607
≤ 10.0.14393.9234 · ≤ 10.0.14393.9234
microsoft
windows 10 1809
≤ 10.0.17763.8880 · ≤ 10.0.17763.8880
microsoft
windows 10 21h2
≤ 10.0.19044.7417 · ≤ 10.0.19044.7417 · ≤ 10.0.19044.7417
microsoft
windows 10 22h2
≤ 10.0.19045.7417 · ≤ 10.0.19045.7417 · ≤ 10.0.19045.7417
microsoft
windows 11 23h2
≤ 10.0.22631.7219
microsoft
windows 11 24h2
≤ 10.0.26100.8655
microsoft
windows 11 25h2
≤ 10.0.26200.8655
microsoft
windows 11 26h1
≤ 10.0.28000.2269
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
≤ 10.0.14393.9234
+3 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)
  • 5 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.2.2
  • V10.4.7
  • V3.7.3
  • V5.3.1

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can block untrusted data from being accepted or processed as if it were trusted.

Input validation directly stops acceptance of untrusted data mixed into trusted inputs.

Associating security attributes with data allows the system to distinguish and reject extraneous untrusted portions.

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 address proper trust-boundary enforcement and input validation, preventing this class of weakness during development.

PR.DS-01 partial match
prevents

Cryptographic integrity checks on data-at-rest can detect tampering or substitution of untrusted content mixed with trusted data.

PR.DS-02 partial match
prevents

Cryptographic integrity mechanisms on data-in-transit can prevent acceptance of extraneous untrusted data by validating origin and detecting modification.

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 the weakness but does not itself implement preventive controls.

prevents

Secure development lifecycle mandates input validation and trust-boundary enforcement that directly prevents acceptance of untrusted data alongside trusted data.

prevents

Application security requirements explicitly call for strict separation and validation of trusted versus untrusted data sources.

prevents

Secure architecture principles require explicit trust boundaries and data-origin checks that mitigate mixing of trusted and untrusted inputs.

prevents

Secure coding standards mandate input sanitization and provenance checks that prevent acceptance of extraneous untrusted data.

none

Information access restriction limits who can supply data but does not address validation of data origin or trust level.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-349

References