AMD Firmware Flaw and Winbond RPMC Weakness Enable TPM Lockout Bypass for Windows Hello and BitLocker PINs

Researchers from Technische Universität Berlin demonstrated a physical attack that resets TPM lockout counters on AMD and some Intel systems, allowing rapid brute-force guessing of short numeric PINs used by Windows Hello and BitLocker. The attack exploits either a firmware verification gap in AMD processors or a voltage-glitch key-leakage issue in Winbond RPMC flash chips to restore the wrong-guess counter after each attempt. In lab tests, a four-digit Hello PIN was recovered in 57 minutes and a six-digit BitLocker PIN in under seven minutes, reducing worst-case recovery times from years to days. AMD confirmed the flaw as CVE-2026-43613 and scheduled firmware fixes through February 2027, while Winbond has not yet committed to a hardware redesign. Microsoft rated the Windows Hello report as moderate severity and plans to raise the default minimum PIN length to six digits. The researchers released attack firmware, board designs, and scripts, noting that successful reproduction requires specialized hardware and physical access.

The Hacker NewsTranslated from English

Read at source

Researchers at Technische Universität Berlin have shown that the TPM lockout mechanism protecting Windows Hello and BitLocker PINs can be bypassed on many AMD-based PCs and some Intel systems through a physical attack that resets the wrong-guess counter.

The attack works because the TPM on these machines is a firmware TPM whose state, including the failure counter, is stored encrypted on the mainboard flash chip. By restoring an earlier copy of that state, an attacker can repeatedly attempt PIN guesses without triggering the documented lockout delays.

Attack Mechanics on AMD Systems

On AMD platforms using RPMC flash, the processor firmware fails to verify that the monotonic counter actually increased after an update. A small interposer board placed between the CPU and flash chip can block the counter write while reporting success, allowing the old state to be restored. On systems without RPMC, simply rewriting an older flash image with a standard programmer resets the counter.

Winbond RPMC chips contain an additional weakness: a brief voltage glitch can extract the secret key used to sign counter values. With that key, an attacker can forge arbitrary counter states, defeating the protection entirely.

Lab Results and Timings

In controlled tests, researchers recovered a four-digit Windows Hello PIN (1235) on an HP OmniBook 3 with an AMD Ryzen AI 5 330 processor after 236 attempts in 57 minutes. A six-digit BitLocker PIN (123457) on a Framework Laptop 13 with an Intel Core Ultra 5 125H and Winbond flash was found in 6 minutes 55 seconds under the same attempt count.

Calculated worst-case times drop dramatically: a four-digit PIN falls from 69 days to roughly 40 hours, while a default six-digit BitLocker PIN falls from 19 years to about 20 days when the lockout is neutralized.

Vendor Responses and Mitigation

AMD acknowledged the firmware issue as CVE-2026-43613 (CVSS 5.1) and plans fixes for most affected Ryzen, Ryzen AI, Threadripper, Athlon, and EPYC processors between November 2026 and February 2027. Intel stated that the research did not demonstrate a vulnerability in an Intel component. Microsoft classified the Windows Hello report as moderate severity and will raise the recommended minimum PIN length to six digits.

Owners of AMD systems can check for RPMC support by running a simple Linux command; systems using Winbond 25R or 74M flash remain exposed until new silicon is available. The researchers recommend increasing PIN length by at least two digits until firmware updates are installed.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

Microsoft Entra Connect Health Flaw Exploited to Access Tenant Metadata and Admin Emails
GnuPG Warns of Critical Double-Free Flaw in GPGME Exposing App Data to Malicious OpenPGP Keys
CISA Adds Four Critical Flaws in Apache Roller, Cisco Expressway, SAP NetWeaver, and VMware vCenter to Known Exploited Vulnerabilities Catalog