Skip to content
Fencer Vulns
high 8.8

CVE-2026-7898 json

Use after free in Chromoting in Google Chrome on Linux prior to 148.0.7778.96 allowed a remote attacker to execute arbitrary code via malic…

published 2026-05-06 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-27899

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 Chromoting in Google Chrome on Linux prior to 148.0.7778.96 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Critical)

Patch / fix

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

debian advisories DEBIAN-CVE-2026-7898

  • chromium openSUSE Leap 16.0 148.0.7778.215-bp160.1.1
  • chromium openSUSE Tumbleweed 148.0.7778.167-1.1

opensuse advisories openSUSE-SU-2026:20849-1openSUSE-SU-2026:10778-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-7898 updated cvss 9.8

chromium-browser: Use after free in Chromoting

  • 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
6 mo ago

Exploit prediction

0.31% 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.