Pass-the-Passkey: a Black Hat researcher found the WebAuthn implementation bugs, not the standard
At Black Hat USA 2026, SpecterOps principal security researcher Michael Grafnetter presented a family of passkey attacks including cleartext YubiKey signatures readable by any authenticated user and a major cloud passkey implementation vulnerable to the exact attack it was built to stop.
At Black Hat USA 2026 this week, SpecterOps principal security researcher Michael Grafnetter presented "Pass-the-Passkey," a family of attacks he describes as fundamentally similar to Pass-the-Hash and NTLM Relay, aimed not at the WebAuthn standard but at how real deployments implement it. The findings include an unnamed major cloud service whose passkey implementation is vulnerable to the very attack class passkeys were designed to prevent, and YubiKey signatures stored in cleartext and readable by any authenticated unprivileged user, including remotely. Grafnetter attributes the pattern to WebAuthn's 22-step validation process, cryptography intricate enough that even a co-author of the standard missed validation steps in its own implementation. The demonstrated techniques, phishing, tampering, spoofing, fuzzing, and prompt-flooding, can impersonate privileged identities while evading both phishing-resistant MFA enforcement and popular XDR detection.
Why it matters
Passkeys are the recommended fix for phishing-resistant authentication, so a talk that breaks specific implementations without breaking WebAuthn/FIDO2 itself is a more useful signal than it sounds: the standard held, the shortcuts vendors took building on top of it didn't. A signature readable in cleartext by any logged-in user turns "phishing-resistant" into a false sense of security the moment an attacker has any foothold on the box.
The practical takeaway isn't to distrust passkeys, it's to stop treating "we deployed passkeys" as a finished project. Ask your identity provider and hardware key vendor directly whether their specific implementation was in scope for this research, and don't assume compliance with the standard means immunity from implementation bugs. A related but independently discovered attack chain against Google's synced passkeys, published the same week, is covered separately.
Source: DSInternals
Related on Start with Identity
- BlogThree passkey attacks land in one week, none of them breaking the cryptography
SpecterOps, Unit 42, and Dirk-jan Mollema each demonstrated ways to defeat passkey protections without attacking WebAuthn itself, through cleartext event logs,
- BlogUnit 42 finds malware can extract Google's synced passkey keys straight out of Chrome's memory
Palo Alto Networks Unit 42 disclosed three attacks, Pass-ta-key, Silver Pass-ta-key, and Golden Pass-ta-key, that extract device identity keys and the master se
- BlogMalware can drive a Windows Hello key for Entra ID persistence without a PIN prompt
Dirk-jan Mollema showed that code running in a signed-in Windows session can use the victim's TPM-bound Windows Hello for Business key as a FIDO2 credential, sa
- PodcastEntra.Chat
A weekly show for Microsoft Entra administrators, with deployment stories from practitioners and the engineers who build the product. Hosted by a Microsoft empl
- PodcastOkta
Okta's 2023 interview series for product managers and marketers on using customer identity to build better experiences. One season, 14 episodes.
- ReportPhishing-Resistant MFA Support Matrix 2026
54% of 95 business SaaS apps support passkeys or security keys, but only 13% let admins require them, and 60% of apps with a documented SSO plan charge more for