VulnSocial

CVE-2026-45642Disclosure(microsoft / windows_10_1607)

LOWCVSS 3.9 · LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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

microsoft CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Vendor / third-party advisories
Weakness type (CWE)
CWE-20

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • windows_10_1607
  • windows_10_1809
  • windows_10_21h2
  • windows_10_22h2

Threat summary

  • 4 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • General: 2 classified signals
  • Peaked 1d ago at 3 mentions (2026-06-09); latest day: 1
  • 4 total mentions across 2 days

Affected systems

Vendors
microsoft
Products
windows_10_1607windows_10_1809windows_10_21h2windows_10_22h2windows_11_23h2windows_11_24h2windows_11_25h2windows_11_26h1windows_server_2012windows_server_2016

2 versions affected across 13 products

Deep dive

Activity timeline4 mentions / 2d
01223Mentions · 2026-06-09: 3Mentions · 2026-06-10: 1Technical Details · 2026-06-09: 206-0906-10
Signal classification2 categories
Disclosure
250.0%
General
250.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-06-093
Disclosure2General1
2026-06-101
General1
Full discourse4 posts
  • Nick Peterson 🇺🇲 ✝️@nickeverdox
    Disclosure

    Up until just recently, some metrics of Microsoft Azure Attestation were completely vulnerable to spoofing in some circumstances, and would accept attacker controlled measurements. SecureBoot in this case, spoofed as ON from a malicious bootkit. see CVE-2026-45642 https://t.co/dvTjuw9jVO

    Post summary

    The tweet announces CVE-2026-45642, describing how Azure Attestation metrics can be spoofed to accept attacker-controlled measurements and that SecureBoot can be spoofed, but it does not provide a PoC, exploit, patch, or claim of active exploitation.

    18331027668220.6K
    3.3K followersView on X
  • Phillip Koskinas@deteccphilippe
    General

    our own @nickeverdox securing the very fabric of this reality. https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45642

    Post summary

    The tweet references Microsoft's security page for CVE-2026-45642 via a link but provides no additional details or context.

    42051620.2K
    9.4K followersView on X
  • Anti-Cheat Police Department 🕵️@AntiCheatPD
    General

    @CallofDuty @nickeverdox Despite claims from the RICOCHET Team that MAA is much harder to crack than local checks its possible to spoof SecureBoot as 'ON' by using a malicious bootkit. https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45642 https://t.co/0qBMOcyBV2

    Post summary

    The tweet states that SecureBoot can be spoofed via a malicious bootkit, challenging previous claims about MAA, and cites CVE‑2026‑45642, but it does not provide a PoC, exploit code, or patch details.

    1004869.0K
    43.5K followersView on X
  • WindowsForum@windowsforum
    Disclosure

    🪟 Another “spoofing” bug in Azure Attestation means the trust handshake could be… faked. If your health proofs can be lied about, your policies are just vibes in a hoodie. #Windows #Microsoft #Azure #Security #CVE https://windowsforum.com/threads/cve-2026-45642-attestation-spoofing-what-windows-azure-teams-must-review.424313/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #DeviceHealthAttestation https://t.co/ydCXFHUAs3

    Post summary

    The tweet announces a spoofing vulnerability in Azure Attestation (CVE‑2026‑45642) that could falsify device health proofs, highlighting potential policy weaknesses.

    0000029
    1.2K followersView on X
CPE platform detail24 entries

24 of 24 entries

PartVendorProductVersionTarget SWTarget HW
OSmicrosoftwindows_10_1607--x64
OSmicrosoftwindows_10_1607--x86
OSmicrosoftwindows_10_1809--x64
OSmicrosoftwindows_10_1809--x86
OSmicrosoftwindows_10_21h2--arm64
OSmicrosoftwindows_10_21h2--x64
OSmicrosoftwindows_10_21h2--x86
OSmicrosoftwindows_10_22h2--arm64
OSmicrosoftwindows_10_22h2--x64
OSmicrosoftwindows_10_22h2--x86
OSmicrosoftwindows_11_23h2--arm64
OSmicrosoftwindows_11_23h2--x64
OSmicrosoftwindows_11_24h2--arm64
OSmicrosoftwindows_11_24h2--x64
OSmicrosoftwindows_11_25h2--arm64
OSmicrosoftwindows_11_25h2--x64
OSmicrosoftwindows_11_26h1--arm64
OSmicrosoftwindows_11_26h1--x64
OSmicrosoftwindows_server_2012---
OSmicrosoftwindows_server_2012r2--
OSmicrosoftwindows_server_2016---
OSmicrosoftwindows_server_2019---
OSmicrosoftwindows_server_2022---
OSmicrosoftwindows_server_2025--x64

Explore more

Back to dashboardmicrosoft CVEswindows_10_1607 vulnerabilities