CVE-2026-106212: Incorrect authorization in Autofill in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveragi

Q: How do I fix CVE-2026-106212?

chrome: upgrade to 155.0.8059.39. Exact commands for each OS are on this page.

Q: Is CVE-2026-106212 being exploited?

CVE-2026-106212 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-106212 affect?

CVE-2026-106212 affects chrome. Severity is high (CVSS 8.8). Incorrect authorization in Autofill in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)

Routine

HIGH 8.8UPGRADE

CVE-2026-106212 is a high-severity flaw (CVSS 8.8) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Incorrect authorization in Autofill in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-863
Published	2026-10-06
Last modified	2026-10-08

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-08 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-10-06 19:17 UTCPublished CVE record published
2026-10-08 14:07 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 155.0.8059.39

Fixed in: 155.0.8059.39

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 155.0.8059.39 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-106212?

chrome: upgrade to 155.0.8059.39. Exact commands for each OS are on this page.

Is CVE-2026-106212 being exploited?

CVE-2026-106212 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-106212 affect?

CVE-2026-106212 affects chrome. Severity is high (CVSS 8.8). Incorrect authorization in Autofill in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)

How urgent is CVE-2026-106212?

Priority 38/100. High severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-0628 HIGH 8.8 UPGRADE Insufficient policy enforcement in WebView tag in Google Chrome prior to 143.0.7499.192 allowed an attacker wh
CVE-2026-5285 HIGH 8.8 UPGRADE Use after free in WebGL in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrar
CVE-2026-6315 HIGH 8.8 UPGRADE Use after free in Permissions in Google Chrome on Android prior to 147.0.7727.101 allowed a remote attacker wh
CVE-2026-6363 HIGH 8.8 UPGRADE Type Confusion in V8 in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to potentially perform
CVE-2026-6311 HIGH 8.3 UPGRADE Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attack

References

← Back to latest CVEs