CVE-2026-17835 json
Inappropriate implementation in Chrome for iOS in Google Chrome on iOS prior to 151.0.7922.72 allowed a remote attacker to perform UI spoof…
published 3mo ago modified 17d ago also EUVD-2026-50584
- cvss
- 6.5
- 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 21%
- public exploits
- 0
- none known
Summary
Inappropriate implementation in Chrome for iOS in Google Chrome on iOS prior to 151.0.7922.72 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
Patch / fix
- google chrome 151.0.7922.72
- chromium Debian 12 151.0.7922.71-1~deb12u1
- chromium Debian 13 151.0.7922.71-1~deb13u1
- chromium Debian 14 151.0.7922.71-1
debian advisories DEBIAN-CVE-2026-17835
- chromium openSUSE Leap 16.0 151.0.7922.173-bp160.1.1
- chromium openSUSE Tumbleweed 151.0.7922.71-1.1
opensuse advisories openSUSE-SU-2026:21624-1openSUSE-SU-2026:11434-1
Is CVE-2026-17835 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
chromereleases.googleblog.com
/2026/07/stable-channel-update-for-desktop_0887107924.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/517801739
permissions-required
Sources
- CVE List CVE-2026-17835
- NVD CVE-2026-17835
Fencer Intel 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.