CVE-2026-13022: Chrome Autofill Origin-Bypass Vulnerability – Patch to 149.0.7827.197

Technical summary

CVE-2026-13022 is an origin-bypass vulnerability in Chrome's Autofill implementation classified under CWE-346 (Origin Validation Error). The flaw permits a compromised renderer process to extract cross-origin data through a malicious HTML page. The vulnerability affects Chrome versions before 149.0.7827.197 and has been assigned a CVSS 3.1 score of 6.5 (Medium). The attack requires network access and user interaction but does not require privilege escalation. The attack vector is network-based, attack complexity is low, and the primary impact is confidentiality loss with no integrity or availability impact.

Business impact

The primary risk is unauthorized disclosure of sensitive autofilled data—credentials, payment information, personal details—from legitimate websites when a user visits a malicious page. Since the vulnerability requires prior renderer process compromise, the threat is elevated in scenarios where users are exposed to malicious ads, drive-by downloads, or compromised legitimate websites. Organizations with strict data-handling compliance requirements (PCI-DSS, HIPAA, GDPR) should treat this as a credential and personally identifiable information exposure vector.

Affected systems

Google Chrome prior to version 149.0.7827.197 is affected across Windows, macOS, and Linux platforms. The vulnerability is browser-specific; affected operating systems (Windows, macOS, Linux kernel) are listed as context for deployment scope but the actual vulnerability exists in the Chrome application itself, not the OS kernel or system libraries.

Exploitability

The vulnerability has a low barrier to exploitation once the renderer process is compromised. However, it is not remotely exploitable in isolation—an attacker must first compromise Chrome's renderer process, typically through a separate browser-based vulnerability, drive-by attack, or malicious content. User interaction is required (visiting a malicious page). Because the renderer is already compromised in the attack chain, the secondary step of crafting malicious HTML is relatively trivial. The vulnerability is not tracked in the CISA KEV catalog, indicating no evidence of active in-the-wild exploitation at publication time.

Remediation

Update Google Chrome to version 149.0.7827.197 or later. The update patches the Autofill implementation to properly validate origin boundaries. Chrome's auto-update mechanism should deploy the patch automatically, but manual verification is recommended for managed deployments. Users on Windows, macOS, and Linux should all prioritize this update.

Patch guidance

Apply Chrome update 149.0.7827.197 or newer as soon as feasible. For enterprise environments, verify patch deployment through your mobile device management (MDM) or endpoint management solution. Chrome typically auto-updates, but confirm via Settings > About Google Chrome that the installed version matches or exceeds 149.0.7827.197. No configuration changes are needed; the patch is transparent to end users.

Detection guidance

Monitor for signs of renderer process compromise as a precursor to exploitation. Review browser crash logs and renderer process termination events—legitimate exploits may leave traces. Endpoint detection and response (EDR) tools should flag unusual child processes spawned from Chrome or unusual inter-process communication. Content Security Policy (CSP) headers and Subresource Integrity (SRI) on legitimate websites provide some mitigation against injected malicious HTML. Network monitoring for malware distribution or drive-by downloads targeting users with outdated Chrome builds can provide early warning.

Why prioritize this

While the CVSS score is medium (6.5), the vulnerability's practical impact warrants prompt attention because: (1) it results in direct confidentiality loss of autofilled sensitive data, (2) it affects a ubiquitous browser across all major platforms, (3) Chrome's auto-update provides a clear remediation path with minimal friction, and (4) it is currently not exploited in-the-wild, offering a window to patch before active campaigns emerge. Organizations should treat this as a high-priority update despite the medium CVSS score due to the reputational and compliance risk of credential leakage.

Risk score, explained

The CVSS 3.1 score of 6.5 (Medium) reflects: Attack Vector Network (increases score), Attack Complexity Low (increases score), Privileges Required None (increases score), User Interaction Required (decreases score relative to no-interaction variants), and Confidentiality Impact High (primary concern) balanced against no Integrity or Availability impact. The score is conservative because exploitation requires renderer compromise as a prerequisite. The severity does not capture the downstream value of the data leaked (credentials, payment info), which organizations should assess independently based on their user base and data sensitivity.

Frequently asked questions