Skip to main content
CVE-2026-11628VulnerabilityPublished

CVE-2026-11628: Google Chrome · Use after free

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium : upgrade to 149.0.7827.103 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 149.0.7827.103
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Google Chrome to 149.0.7827.103.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=149.0.7827.103 <149.0.7827.103
Fixed in
  • 149.0.7827.103

AI-suggested

A fix is available in Google Chrome version 149.0.7827.103 and later. Users should update to this version or newer to remediate the vulnerability. Since this is not a cloud service, remediation depends on applying the vendor's update. Refer to the official Google Chrome stable channel update advisory for detailed patch information.

Description

Use after free in Ozone in Google Chrome prior to 149.0.7827.103 allowed a local attacker to potentially exploit heap corruption via physical access to the device. (Chromium security severity: Critical)

References

Community reviews

Loading reviews…