Chrome is a ubiquitous enterprise browser; this high-severity autofill bug can exfiltrate sensitive user data and should be triaged broadly across IT teams.
CVE-2026-106225
Chrome autofill authorization bug lets crafted pages steal autofill data.
Is CVE-2026-106225 being exploited?
Not confirmed. CVE-2026-106225 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. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-106225?
CVE-2026-106225 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-106225?
Yes. A fix has been recorded for CVE-2026-106225. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-106225 affect?
CVE-2026-106225 affects Google Chrome < 155.0.8059.39 (desktop), Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-106225?
Update Chrome to 155.0.8059.39+ and advise users to avoid untrusted pages.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can use a crafted page and social engineering to obtain autofill data (passwords, addresses, payment info) from users' browsers.
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.