Skip to main content
VulnerabilityPublished Updated

CVE-2026-9949: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 148.0.7778.216 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 148.0.7778.216
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Upgrade Google Chrome to 148.0.7778.216.

Affected software

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

AI-suggested

The vendor advisory references a stable channel update for Chrome released on May 28, 2026, which likely includes a fix for this vulnerability. However, the explicit patch or remediation status is not confirmed in the provided data. Users should update to Chrome version 148.0.7778.216 or later to mitigate this issue. Until confirmation is obtained, users should monitor the vendor advisory for official patch and remediation guidance.

Description

CVE-2026-9949 is a use-after-free vulnerability in the core component of Google Chrome on Windows versions prior to 148.0.7778.216. This flaw could allow a remote attacker who has already compromised the renderer process to potentially escape the browser sandbox by using a specially crafted HTML page. The vulnerability has a high severity rating with a CVSS score of 8.3. No known exploits in the wild have been reported at the time of publication.

References

Community reviews

Loading reviews…