Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Unrated

Cross-origin data leak in Google Chrome Autofill

IdentifiersCVE-2026-13022CWE-284

CVE-2026-13022 is a high-severity inappropriate implementation vulnerability in the Autofill component of Google Chrome prior to 149.0.7827.197. According to the provided advisory, a remote attacker who has already compromised the renderer process can use a crafted HTML page to cause Chrome Autofill to leak cross-origin data. The issue is described as an implementation flaw rather than a memory-safety bug, indicating a security boundary or policy enforcement failure in Autofill’s handling of data across origins.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker operating from a compromised renderer process to disclose cross-origin data that should not be accessible to the attacking origin. This is an information disclosure and security restriction bypass issue that can expose sensitive data handled or surfaced through Autofill-related browser contexts.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is provided in the supplied content. Mitigation is limited to reducing exposure until patching is complete: prioritize rapid browser updates, restrict use of outdated Chromium-based browsers, and monitor for renderer-compromise chains that could be paired with this bug. Because exploitation requires a compromised renderer process, reducing exposure to renderer RCE or sandbox-bypass precursors also lowers risk.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 149.0.7827.197 or later. For Chromium on Debian stable (trixie), apply the vendor security update and upgrade to 149.0.7827.196-1~deb13u1 or a later patched package. Downstream Chromium-based browsers should be updated once vendor patches are available.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DebianChromiumapplication
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.