CVE-2026-121172 json
Incorrect authorization in Isolated in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to spoof UI elements via a crafted HT…
published 2026-11-03 5 d ago modified 2026-11-05 3 d ago also EUVD-2026-116338
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Incorrect authorization in Isolated in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to spoof UI elements via a crafted HTML page. (Chromium security severity: Low)
Patch / fix
- google chrome 157.0.8103.38
- chromium openSUSE Tumbleweed 157.0.8103.38-1.1
opensuse advisories openSUSE-SU-2026:12426-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-121172 updated cvss 4.3
chromium-browser: Incorrect authorization in Isolated
-
Red Hat All currently supported Red Hat productsnot 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
- partial
- Assessed
- 4 d ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/11/stable-channel-update-for-desktop.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/553270515
permissions-required
Sources
- CVE List CVE-2026-121172
- NVD CVE-2026-121172
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.