Skip to content
Fencer Vulns
high 7.4

CVE-2026-91734 json

Incorrect authorization in Core in Google Chrome on on Windows prior to 153.0.8010.47 allowed a local attacker to execute arbitrary code ou…

published 2026-09-15 54 d ago modified 2026-09-17 53 d ago also EUVD-2026-79959

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

Summary

Incorrect authorization in Core in Google Chrome on on Windows prior to 153.0.8010.47 allowed a local attacker to execute arbitrary code outside the sandbox via a local program. (Chromium security severity: High)

Patch / fix

  • google chrome 153.0.8010.47
  • chromium Debian 12 153.0.8010.52-1~deb12u1
  • chromium Debian 13 153.0.8010.47-2~deb13u1
  • chromium Debian 14 153.0.8010.47-1

debian advisories DEBIAN-CVE-2026-91734

  • chromium openSUSE Leap 16.0 153.0.8010.52-bp160.1.1
  • chromium openSUSE Tumbleweed 153.0.8010.47-1.1

opensuse advisories openSUSE-SU-2026:21921-1openSUSE-SU-2026:11812-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-91734 updated cvss 8.8

chromium-browser: chromium-browser: Incorrect authorization in Core

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

Exploit prediction

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

CVSS scores

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