Executive Summary
In August 2026, Unit 42 researchers identified three attack vectors—Pass-ta-key, Silver Pass-ta-key, and Golden Pass-ta-key—targeting Google Password Manager's passkey authentication on Windows systems with Trusted Platform Modules (TPMs). These methods allow malware with user-level privileges to bypass biometric or PIN verification, enabling unauthorized access to passkey-protected accounts. The attacks exploit weaknesses in Chrome's handling of device keys, re-enrollment processes, and user verification checks, potentially granting attackers persistent access to sensitive credentials.
This discovery underscores the evolving nature of authentication bypass techniques and highlights the necessity for organizations to reassess the security of passkey implementations. As passkeys gain popularity for their phishing-resistant properties, ensuring robust implementation and validation mechanisms becomes critical to prevent exploitation by sophisticated malware.
Why This Matters Now
The emergence of these attack vectors against passkey systems highlights the urgent need for organizations to evaluate and strengthen their authentication mechanisms. As passkeys are increasingly adopted for their security benefits, ensuring their resilience against such sophisticated attacks is paramount to maintaining trust and protecting sensitive information.
Attack Path Analysis
Malware running as an ordinary user on a Windows machine can sign into a victim's passkey-protected accounts without a fingerprint, a PIN, or anything at all appearing on the victim's screen. Unit 42 detailed three attack paths against Chrome's Google Password Manager cloud authenticator, which it calls Pass-ta-key, Silver Pass-ta-key and Golden Pass-ta-key; the strongest targets the master key protecting the user's synced passkeys. None of this breaks the cryptography. The attacks go after the code around the passkey: how Chrome stores its device keys, how it re-enrolls a device after that state disappears, and whether the site you are signing into bothers to check that a human was verified at all. The attacks can silently obtain a valid authentication assertion, install an attacker-controlled user-verification key, or extract the 32-byte Security Domain Secret (SDS) used to decrypt synced passkey private keys. The researchers said the last two paths can provide reusable access from an attacker's own environment after the initial endpoint compromise. The report does not describe exploitation in the wild and gives no CVE identifiers, affected Chrome versions, or complete remediation status. A search of the National Vulnerability Database on August 3, 2026, found no CVE matching the three named techniques. The research is limited to Google Password Manager in Chrome on Windows systems equipped with a Trusted Platform Module (TPM), and every path begins with malware already running on the victim's device. Chromium source as of August 3 corroborates parts of the architecture, not that the latest stable Chrome release remains exploitable. These are post-compromise techniques. They describe what an attacker reaches on a machine already lost, not how the machine was lost. The attack begins with local reconnaissance. Chrome stores synchronized credential records under %LocalAppData%\Google\Chrome\User Data\<Profile>\Sync Data\LevelDB. The researchers said an unprivileged process can read enough metadata to identify the relying parties and usernames tied to the victim's passkeys, along with credential identifiers and encrypted private-key material.
Kill Chain Progression
Initial Compromise
Description
Malware is introduced onto the victim's Windows machine, operating with ordinary user privileges.
Related CVEs
CVE-2026-11151
CVSS 7.5Insufficient validation of untrusted input in Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Affected Products:
Google Chrome – < 149.0.7827.53
Exploit Status:
no public exploitCVE-2026-11032
CVSS 6.5Inappropriate implementation in Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Affected Products:
Google Chrome – < 149.0.7827.53
Exploit Status:
no public exploitCVE-2026-11084
CVSS 6.5Inappropriate implementation in Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Affected Products:
Google Chrome – < 149.0.7827.53
Exploit Status:
no public exploitCVE-2026-11011
CVSS 8.1Insufficient policy enforcement in Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page.
Affected Products:
Google Chrome – < 149.0.7827.53
Exploit Status:
no public exploitCVE-2026-12446
CVSS 4.3Inappropriate implementation in Passwords in Google Chrome prior to 149.0.7827.155 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Affected Products:
Google Chrome – < 149.0.7827.155
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Credentials from Password Stores: Password Managers
Credentials from Password Stores: Credentials from Web Browsers
Browser Session Hijacking
Forge Web Credentials
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Strong Authentication for Users
Control ID: 8.3.1
NYDFS 23 NYCRR 500 – Multi-Factor Authentication
Control ID: 500.12
DORA – ICT Risk Management Framework
Control ID: Article 6
CISA ZTMM 2.0 – Identity and Access Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
Google Password Manager authentication bypass attacks threaten banking credentials, enabling malware to silently access passkey-protected financial accounts without user verification.
Computer Software/Engineering
Authentication bypass vulnerabilities in Chrome's Password Manager expose software development environments where engineers store critical system credentials and source code access.
Health Care / Life Sciences
Passkey hijacking attacks compromise healthcare worker access to patient systems, violating HIPAA compliance requirements and enabling unauthorized medical record access.
Government Administration
Government agencies using Chrome Password Manager face credential theft risks from malware extracting security domain secrets, compromising classified system authentication.
Sources
- Google Password Manager Attacks Could Let Malware Hijack Passkey-Protected Accountshttps://thehackernews.com/2026/08/google-password-manager-attacks-could.htmlVerified
- CVE-2026-11151: Google Chrome Password Manager Sandbox Escape Vulnerabilityhttps://sec.co/vulnerabilities/cve-2026-11151Verified
- CVE-2026-11032: Chrome Password Manager Cross-Origin Data Leakhttps://sec.co/vulnerabilities/cve-2026-11032Verified
- CVE-2026-11084: Chrome Password Manager Cross-Origin Data Leak (v149.0.7827.53)https://sec.co/vulnerabilities/cve-2026-11084Verified
- CVE-2026-11011: Chrome Password Manager Site Isolation Bypass – Patch Guidancehttps://sec.co/vulnerabilities/cve-2026-11011Verified
- CVE-2026-12446: Google Chrome Information Disclosure Flawhttps://www.sentinelone.com/vulnerability-database/cve-2026-12446/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it can limit the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and identity-aware policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: While Aviatrix CNSF may not prevent the initial malware execution, it could limit the malware's ability to communicate with other workloads, reducing the potential for further compromise.
Control: Zero Trust Segmentation
Mitigation: Aviatrix Zero Trust Segmentation could limit the malware's ability to access sensitive accounts by enforcing strict identity-based access controls.
Control: East-West Traffic Security
Mitigation: Aviatrix East-West Traffic Security could limit the attacker's ability to move laterally by enforcing strict controls on internal communications.
Control: Multicloud Visibility & Control
Mitigation: Aviatrix Multicloud Visibility & Control could limit the attacker's ability to maintain control over compromised accounts by providing comprehensive monitoring and control across cloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Aviatrix Egress Security & Policy Enforcement could limit the attacker's ability to exfiltrate data by enforcing strict outbound traffic policies.
While Aviatrix CNSF may not prevent the initial unauthorized access, it could limit the overall impact by reducing the attacker's ability to move laterally and exfiltrate data.
Impact at a Glance
Affected Business Functions
- User Authentication
- Account Security
- Data Protection
Estimated downtime: N/A
Estimated loss: N/A
Potential exposure of user credentials and passkey-protected accounts.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to restrict malware's ability to access sensitive areas of the system.
- • Enforce East-West Traffic Security to monitor and control internal communications, limiting lateral movement.
- • Utilize Multicloud Visibility & Control to detect and respond to unauthorized access attempts across cloud environments.
- • Apply Egress Security & Policy Enforcement to prevent exfiltration of sensitive data.
- • Deploy Threat Detection & Anomaly Response systems to identify and mitigate unusual activities indicative of compromise.



