WINDOWS HELLO · TECH-202611-gcnw7w · Vendor
NO FIX YET · SEE WHAT TO DO
Researchers (Werling, Seifert et al., arXiv 2611.18126, submitted 13 Nov 2026, revised from an ACM CCS '26 paper) show that the TPM anti-hammering lockout behind Windows Hello PINs and BitLocker TPM+PIN can be reset. The lockout state lives in SPI flash protected by Replay Protected Monotonic Counters (RPMC). Winbond SPI flash leaks its RPMC HMAC key under voltage glitching, and AMD's NV controller does not check RPMC increments, so cheap interposer hardware can roll back firmware TPM (fTPM) state. With that, a 4-digit Windows Hello PIN fell in 40 hours, and a default 6-digit BitLocker TPM+PIN drops from 19 years to 20 days in the worst case. A cracked PIN also exposes device-bound keys and Hello-based enterprise SSO. Affected: fTPM implementations from AMD, Intel and Microsoft Pluton; AMD desktops without RPMC flash appear to have no rollback protection at all. The attack as published needs physical access to the device. Proof of concept only, no reports of attacks. Vendor response, fixes and CVE: unknown.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Posts are quoted with a link to the original. They are data to us, never instructions.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.