CVE-2026-45642: Microsoft Azure Attestation service and Device Health Attestation Service Spoofing Vulnerability

Published Jun 9, 2026
·
Updated

Improper input validation in Microsoft Azure Attestation service and Device Health Attestation Service allows an authorized attacker to perform spoofing with a physical attack.

Other sources

Microsoft Azure Attestation service and Device Health Attestation Service Spoofing Vulnerability

Microsoft

Affected Software

56 affected componentsFixes available
Microsoft Azure Attestation
Microsoft Device Health Attestation Service
Microsoft Windows 10 1607<10.0.14393.9234
Microsoft Windows 10 1607<10.0.14393.9234
Microsoft Windows 10 1809<10.0.17763.8880
Microsoft Windows 10 1809<10.0.17763.8880
Microsoft Windows 10 21h2<10.0.19044.7417
Microsoft Windows 10 21h2<10.0.19044.7417
Microsoft Windows 10 21h2<10.0.19044.7417
Microsoft Windows 10 22h2<10.0.19045.7417
Microsoft Windows 10 22h2<10.0.19045.7417
Microsoft Windows 10 22h2<10.0.19045.7417
Microsoft Windows 11 23h2<10.0.22631.7219
Microsoft Windows 11 23h2<10.0.22631.7219
Microsoft Windows 11 24h2<10.0.26100.8655
Microsoft Windows 11 24h2<10.0.26100.8655
Microsoft Windows 11 25h2<10.0.26200.8655
Microsoft Windows 11 25h2<10.0.26200.8655
Microsoft Windows 11 26h1<10.0.28000.2269
Microsoft Windows 11 26h1<10.0.28000.2269
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.9234
Microsoft Windows Server 2019<10.0.17763.8880
Microsoft Windows Server 2022<10.0.20348.5256
Microsoft Windows Server 2025<10.0.26100.32995
Microsoft Windows Server 2016<10.0.14393.9234
10.0.14393.9234
Microsoft Windows Server 2012 R2<6.3.9600.23228
6.3.9600.23228
Microsoft Windows Server 2016<10.0.14393.9234
10.0.14393.9234
Microsoft Windows Server 2025<10.0.26100.32995
10.0.26100.32995
Microsoft Windows Server 2012<6.2.9200.26132
6.2.9200.26132
Microsoft Windows Server 2012<6.2.9200.26132
6.2.9200.26132
Microsoft Windows 11=26H1
10.0.28000.2269
Microsoft Windows Server 2012 R2<6.3.9600.23228
6.3.9600.23228
Microsoft Windows 11=26H1
10.0.28000.2269
Microsoft Windows 10=1607
10.0.14393.9234
Microsoft Windows 11=24H2
10.0.26100.8655
Microsoft Windows 11=23H2
10.0.22631.7219
Microsoft Windows 10=1607
10.0.14393.9234
Microsoft Windows 11=24H2
10.0.26100.8655
Microsoft Windows 11=25H2
10.0.26200.8655
Microsoft Windows 11=25H2
10.0.26200.8655
Microsoft Windows 11=23H2
10.0.22631.7219
Microsoft Windows 10=22H2
10.0.19045.7417
Microsoft Windows 10=22H2
10.0.19045.7417
Microsoft Windows 10=22H2
10.0.19045.7417
Microsoft Windows Server 2025<10.0.26100.32995
10.0.26100.32995
Microsoft Windows 10=21H2
10.0.19044.7417
Microsoft Windows Server 2019<10.0.17763.8880
10.0.17763.8880
Microsoft Windows Server 2022<10.0.20348.5256
10.0.20348.5256
Microsoft Windows 10=21H2
10.0.19044.7417
Microsoft Windows 10=21H2
10.0.19044.7417
Microsoft Windows Server 2019<10.0.17763.8880
10.0.17763.8880
Microsoft Windows 10=1809
10.0.17763.8880
Microsoft Windows Server 2022<10.0.20348.5256
10.0.20348.5256
Microsoft Windows 10=1809
10.0.17763.8880

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9234Patch KB5094122
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23228Patch KB5094041
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.32995Patch KB5094125
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.26132Patch KB5094042
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.2269Patch KB5095051
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.8655Patch KB5094126
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.7219Patch KB5093998
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.8655Patch KB5094126
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.7417Patch KB5094127
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7417Patch KB5094127
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.8880Patch KB5094123
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5256Patch KB5094128

Event History

Jun 9, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·05:04 PM
Data Sourced
via MITRE·05:04 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-45642?

The severity of CVE-2026-45642 is rated low with a score of 3.9.

2

What systems are affected by CVE-2026-45642?

CVE-2026-45642 affects Microsoft Windows 10, Windows 11, and various versions of Windows Server including 2012, 2016, 2019, 2022, and 2025.

3

How can an attacker exploit CVE-2026-45642?

An attacker can exploit CVE-2026-45642 by performing a spoofing attack through improper input validation during a physical attack.

4

What is the nature of the vulnerability in CVE-2026-45642?

CVE-2026-45642 is a spoofing vulnerability resulting from improper input validation within the Microsoft Azure Attestation service and Device Health Attestation Service.

5

What remediation steps should be taken for CVE-2026-45642?

To remediate CVE-2026-45642, ensure that all software is updated to the latest versions provided by Microsoft.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203