Skip to content
Fencer Vulns
high 8.8

CVE-2026-110915 json

Use after free in Compositing in Google Chrome prior to 155.0.8059.84 allowed a remote attacker to execute arbitrary code inside the sandbo…

published 2026-10-15 24 d ago modified 2026-10-19 20 d ago also EUVD-2026-102518

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

Summary

Use after free in Compositing in Google Chrome prior to 155.0.8059.84 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Patch / fix

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

debian advisories DEBIAN-CVE-2026-110915

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

opensuse advisories openSUSE-SU-2026:22124-1openSUSE-SU-2026:12188-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-110915 updated cvss 6.5

chromium-browser: Use after free in Compositing

  • 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
25 d ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.