Cyber Resilience

CVE-2026-58540

Access Control in Microsoft Windows 10 21H2 ≤ 10.0.19044.7548

Published
14 July 2026
Modified
22 July 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.0028 20th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-58540 is a high-severity Improper Authorization (CWE-285) vulnerability in Microsoft Windows 10 21H2. 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 20th 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-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper authorization in Windows Installer allows an authorized attacker to elevate privileges locally.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Why these techniques?

Local privilege escalation via improper authorization in Windows Installer directly matches Exploitation for Privilege Escalation (T1068).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-50346Same product: Microsoft Windows 10 1607
CVE-2026-50344Same product: Microsoft Windows 10 1607
CVE-2026-54121Same product: Microsoft Windows 10 1607
CVE-2026-49170Same product: Microsoft Windows 10 1809
CVE-2026-27912Same product: Microsoft Windows Server 2012
CVE-2025-21275Same product: Microsoft Windows 10 21H2
CVE-2025-24053Same vendor: Microsoft
CVE-2025-21400Same vendor: Microsoft
CVE-2026-42902Same vendor: Microsoft
CVE-2025-53795Same vendor: Microsoft

Affected Assets

microsoft
windows 10 1607
≤ 10.0.14393.9339 · ≤ 10.0.14393.9339
microsoft
windows 10 1809
≤ 10.0.17763.9020 · ≤ 10.0.17763.9020
microsoft
windows 10 21h2
≤ 10.0.19044.7548 · ≤ 10.0.19044.7548 · ≤ 10.0.19044.7548
microsoft
windows 10 22h2
≤ 10.0.19045.7548 · ≤ 10.0.19045.7548 · ≤ 10.0.19045.7548
microsoft
windows 11 24h2
≤ 10.0.26100.8875 · ≤ 10.0.26100.8875
microsoft
windows 11 25h2
≤ 10.0.26200.8875 · ≤ 10.0.26200.8875
microsoft
windows 11 26h1
≤ 10.0.28000.2269 · ≤ 10.0.28000.2269
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
≤ 10.0.14393.9339
microsoft
windows server 2019
≤ 10.0.17763.9020
+2 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • CM-5 Access Restrictions for Change
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization decisions that are improperly implemented, allowing the local privilege escalation in Windows Installer.

prevent

Limits privileges available to an authorized user, reducing the impact of any authorization bypass in the installer.

prevent

Restricts access to perform system changes via the installer, mitigating unauthorized elevation paths.

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.AA-05 mostly match
prevents

PR.AA-05 mostly prevents CWE-285 via enforced policy, reviews, and least-privilege authorization decisions, yet CWE-285 remains only partially prevented because code-level check omissions or errors can still occur outside that single control.

PR.PS-06 mostly match
prevents

Secure SDLC practices catch and eliminate most authorization defects before release, yet a single broad outcome cannot address every design, role, and runtime facet of CWE-285.

PR.AA-01 partial match
prevents

PR.AA-01 supplies managed identities and access-request workflows that can support downstream authorization decisions, yet does nothing to enforce or verify authorization checks inside a product, leaving CWE-285 fully unaddressed by this control alone.

PR.IR-01 partial match
prevents

Network segmentation/zero-trust limits external reachability (partial prevention of exploitation) but leaves application-level authorization logic untouched, so the CWE remains fully introducible and only one facet of its risk is addressed.

PR.PS-05 none match
prevents

PR.PS-05 blocks unauthorized binaries/DNS while CWE-285 is an in-product authorization-check defect, so the control neither prevents the weakness nor removes any of its risk.

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.

prevents

Granular, policy-driven assignment of permissions and dynamic enforcement of those permissions prevent the incorrect or missing authorization decisions that lead to improper authorization flaws.

prevents

By requiring documented authorization rules and periodic policy reviews, the control makes it less likely that authorization decisions will be omitted or implemented inconsistently across applications.

prevents

Mapping access rights to information classification and business requirements forces correct enforcement of authorization decisions, blocking the incorrect authorization weakness at the policy and implementation stage.

detects

Independent reviewers evaluate whether authorization logic matches policy, thereby reducing the window in which incorrect or missing authorization checks remain in production.

detects

By requiring managers to verify that authorization decisions match policy and to remediate deviations, the control limits the persistence of incorrect or missing authorization checks.

prevents

Requiring authorization processes and privilege assignments to be specified during project initiation prevents downstream components from receiving overly broad or incorrect rights that would allow unauthorized actions.

References