Skip to content
Fencer Vulns
medium 6.5

CVE-2026-5905 json

Incorrect security UI in Permissions in Google Chrome on Windows prior to 147.0.7727.55 allowed a remote attacker to perform domain spoofin…

published 2026-04-08 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-20730

cvss
6.5
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 security UI in Permissions in Google Chrome on Windows prior to 147.0.7727.55 allowed a remote attacker to perform domain spoofing via a crafted HTML page. (Chromium security severity: Low)

Patch / fix

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

debian advisories DEBIAN-CVE-2026-5905

  • chromium openSUSE Leap 16.0 147.0.7727.137-bp160.1.1
  • chromium openSUSE Tumbleweed 147.0.7727.55-1.1

opensuse advisories openSUSE-SU-2026:20660-1openSUSE-SU-2026:10530-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-5905 updated cvss 4.3

chromium-browser: Incorrect security UI in Permissions

  • 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
partial
Assessed
7 mo 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 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-451 User Interface (UI) Misrepresentation of Critical Information
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.