News Security news
Hello Again: an attacker holding your PC can bypass the TPM lockout and guess short Windows Hello and BitLocker PINs
On 13 November 2026, researchers at Technische Universität Berlin published “Hello Again”. They show that on many AMD PCs and some Intel PCs, someone who opens the case can roll back the firmware TPM's wrong-guess counter. A four-digit Windows Hello PIN then falls in roughly 40 hours instead of 69 days. The defence is simple: a longer PIN.
Key points
- Firmware TPMs keep their wrong-guess counter in the SPI flash on the motherboard; RPMC counters in the flash chip are meant to stop it being rolled back.
- The researchers found two critical flaws: Winbond flash leaks its HMAC key under voltage glitching, and AMD's controller never checks that the counter actually went up.
- Worst case: a four-digit Windows Hello PIN in about 40 hours instead of 69 days, and a default six-digit BitLocker PIN in 20 days instead of 19 years.
- Intel says no Intel component is vulnerable; Microsoft is raising the suggested Hello PIN length to six digits in a Windows 11 test build.
What happened
Six researchers at Technische Universität Berlin published Hello Again on arXiv on 13 November 2026. They looked at how firmware TPMs on x86 PCs protect the counter of wrong PIN attempts. That counter is what makes a short four-digit Windows Hello PIN acceptable: after a few misses, the TPM locks out further guesses. Intel responded with an announcement on 16 November.
How the attack works
A firmware TPM has no storage of its own, so it keeps its state, including the lockout counter, in the SPI flash on the motherboard. To stop an attacker simply restoring an older copy, newer platforms rely on RPMC (Replay Protected Monotonic Counters): counters inside the flash chip that can only go up and that answer with a signature. Using cheap hardware placed between the CPU and the flash, the researchers say they found several implementation flaws, two of them critical:
- Winbond flash leaks its HMAC key under voltage glitching, so an attacker can forge counter replies.
- AMD's controller never checks that the counter really increased after a write, so the inserted hardware can quietly suppress the increment.
On two AMD desktops without RPMC, the authors say reflashing an older image was enough. The end result is a rollback of fTPM state, lockout counters included, on AMD, Intel and Pluton systems.
Who is affected
In the worst case, the authors estimate a four-digit Windows Hello PIN at about 40 hours instead of 69 days, and a default six-digit BitLocker PIN (the TPM+PIN pre-boot protector) at 20 days instead of 19 years. A recovered Hello PIN also unlocks device-bound keys and Hello-based enterprise single sign-on. The attack needs physical access and an opened case, so the realistic scenario is a lost or stolen laptop.
Intel says the research "did not demonstrate a vulnerability in an Intel component" and that the attack did not succeed on its platforms without a vulnerable third-party flash device. According to The Hacker News, AMD has confirmed a firmware flaw and plans fixes through February 2027; we could not load AMD's bulletin to verify this, so we do not give a CVE number or versions. In Windows 11 test build 29708, released on 13 November, Microsoft set a six-digit minimum for personal-account Hello PINs, with an option for four.
How to check whether a PC is exposed
- CPU: Settings → System → About, the Processor line (Linux:
lscpu). The authors count AMD PCs as affected regardless of flash vendor. - Linux:
grep . /sys/bus/pci/drivers/ccp/*/rpmc_*shows whether RPMC is present and enabled;fwupdmgr securitylists an "AMD SPI Replay protections" entry. The authors note that missing files do not prove RPMC is absent. - Physically: Winbond RPMC chips are marked 25R or 74M, according to the authors.
The attack leaves no trace in Windows: it tampers with hardware outside the running OS.
What to do
- Lengthen the PIN for Windows Hello and BitLocker by at least two digits; a PIN with letters is better.
- In managed fleets, set the Windows Hello for Business minimum PIN length policy (Administrative Templates → System → PIN Complexity) and, for BitLocker, "Configure minimum PIN length for startup"; consider "Allow enhanced PINs for startup" as well (Microsoft documentation).
- AMD PCs: watch for firmware (BIOS/UEFI) updates from your laptop maker and install them once released. Until then, don't leave the device unattended.
- Treat a lost or stolen laptop as a possible breach: lock the device, change account passwords and revoke sessions. See our guide Stolen phone: what to do for the account side.
Timeline
- January and April 2025 - the researchers report the weakness to Winbond, according to THN
- 13 Nov 2026 - Hello Again paper on arXiv; Microsoft ships build 29708 with longer PINs
- 16 Nov 2026 - Intel announcement 2026-11-16-001
FAQ
Can someone guess my PIN this way remotely?
No. According to the researchers, the attack needs physical access, an opened case, custom hardware wired to the flash bus and hours to days of time. It matters mostly for lost, stolen or seized devices.
Is a longer PIN enough?
It helps a lot. Every extra digit multiplies the number of possibilities, and the attack time, by ten. The researchers recommend adding at least two digits; a PIN with letters (an enhanced PIN, in BitLocker terms) is better still.
Am I affected if I have an Intel PC?
According to the researchers, only if the PC uses vulnerable Winbond RPMC flash. Intel says the attack did not succeed on its platforms without a vulnerable third-party flash device and advises asking your PC maker about updates.
Sources
- arXiv - Hello Again: Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello PINs (13 Nov 2026)
- Intel - Security Announcement 2026-11-16-001 "Hello Again" (16 Nov 2026)
- Microsoft - Windows 11 Insider Experimental Preview Build 29708.1003 (13 Nov 2026)
- Microsoft - Configure BitLocker (startup PIN policies)
- The Hacker News - New Attack Bypasses TPM Lockout (18 Nov 2026)
Spotted a mistake? Let us know and we will correct it openly.