Widespread Google Chrome vulnerability enabling theft of autofill data; affects many organizations and users across industries, warranting broad IT/infosec notification.
CVE-2026-106212
Chrome autofill auth flaw allows crafted pages to steal autofill data.
Is CVE-2026-106212 being exploited?
Not confirmed. CVE-2026-106212 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-106212?
CVE-2026-106212 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-106212?
Yes. A fix has been recorded for CVE-2026-106212. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-106212 affect?
CVE-2026-106212 affects Google Chrome <155.0.8059.39 (desktop), Chromium-based browsers prior to fixed build. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-106212?
Update Chrome to 155.0.8059.39 or later and deploy to all endpoints immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can use a crafted HTML page and social engineering to exfiltrate users' autofill data (personal info, payment details).
Immediate action required
- affected< 155.0.8059.39
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.