CVE-2026-12007: Use after free in Core in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker to execut

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

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

Q: Is CVE-2026-12007 being exploited?

CVE-2026-12007 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-12007 affect?

CVE-2026-12007 affects chrome. Severity is high (CVSS 8.8). Use after free in Core in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

Routine

HIGH 8.8UPGRADE

CVE-2026-12007 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.

Use after free in Core in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

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 79%)
CISA exploited list	No
Weakness	CWE-416
Published	2026-06-11
Last modified	2026-10-26

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2026-06-11 22:16 UTCPublished CVE record published
2026-10-26 11:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 149.0.7827.115

Fixed in: 149.0.7827.115

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 149.0.7827.115 (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-12007?

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

Is CVE-2026-12007 being exploited?

CVE-2026-12007 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-12007 affect?

CVE-2026-12007 affects chrome. Severity is high (CVSS 8.8). Use after free in Core in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

How urgent is CVE-2026-12007?

Priority 36/100. High severity

Software pages

Windows vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-113344 HIGH 8.8 UPGRADE Use after free in Performance in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arb
CVE-2026-8510 HIGH 7.5 UPGRADE Integer overflow in Skia in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker who had
CVE-2026-8517 HIGH 8.8 UPGRADE Object lifecycle issue in WebShare in Google Chrome on Mac prior to 148.0.7778.168 allowed a remote attacker w
CVE-2026-8509 HIGH 8.8 UPGRADE Heap buffer overflow in WebML in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute ar
CVE-2026-8524 HIGH 8.8 UPGRADE Out of bounds write in WebAudio in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute

References

← Back to latest CVEs