Skip to content
Fencer Vulns
critical 9.6

CVE-2026-118306 in the critical feed json

Use after free in FileSystem in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code outside the sandbo…

published 2026-10-27 12 d ago modified 2026-11-03 5 d ago also EUVD-2026-111423

cvss
9.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

Use after free in FileSystem in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

Patch / fix

  • google chrome 156.0.8078.73
  • chromium Debian 12 156.0.8078.73-1~deb12u1
  • chromium Debian 13 156.0.8078.73-1~deb13u1
  • chromium Debian 14 156.0.8078.73-1

debian advisories DEBIAN-CVE-2026-118306

  • chromium openSUSE Tumbleweed 156.0.8078.73-1.1
  • chromium openSUSE Leap 16.0 156.0.8078.73-bp160.1.1

opensuse advisories openSUSE-SU-2026:12359-1openSUSE-SU-2026:22202-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-118306 updated cvss 9.6

chromium-browser: Memory corruption in FileSystem

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
11 d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.