Skip to main content
VulnerabilityPublished

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

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 148.0.7778.96 soon.

Data as of 29 Oct 2026, 19:04 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 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 29 Oct 2026.

What to do

Upgrade Google Chrome to 148.0.7778.96.

Affected software

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

AI-suggested

Users should update Google Chrome to version 148.0.7778.96 or later, where this vulnerability has been addressed. The vendor advisory confirms that the fix is included in the stable channel update. No additional mitigation steps are indicated.

Description

CVE-2026-7938 is a use-after-free vulnerability in the CSS component of Google Chrome versions prior to 148.0.7778.96. This flaw allows a remote attacker to execute arbitrary code within the browser's sandbox by delivering a crafted HTML page. The vulnerability has a high severity rating with a CVSS score of 8.8. There are no known exploits in the wild at this time. The vendor advisory linked indicates a stable channel update addressing this issue was released, implying a fix is available in version 148.0.

References

Community reviews

Loading reviews…