CVE-2026-95288: UI misrepresentation in Mobile
Chromium CVE-2026-95288: UI misrepresentation in Mobile
Other sources
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
UI misrepresentation in Mobile in Google Chrome on on iOS prior to 154.0.8037.57 allowed a remote attacker to spoof UI elements via a crafted HTML page. (Chromium security severity: Low)
— NVD
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 154.0.8037.57 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 154.0.4258.37 - Upgrade
Upgrade
Google Chrome on iOSto a version that resolves this vulnerability.Fixed in 154.0.8037.57
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-95350
- CVE-2026-95357
- CVE-2026-95339
- CVE-2026-95281
- CVE-2026-95313
- CVE-2026-95349
- CVE-2026-95284
- CVE-2026-95322
- CVE-2026-95329
- CVE-2026-95356
- CVE-2026-95310
- CVE-2026-95301
- CVE-2026-95291
- CVE-2026-95355
- CVE-2026-95315
- CVE-2026-95298
- CVE-2026-95372
- CVE-2026-95324
- CVE-2026-95283
- CVE-2026-95293
- CVE-2026-95274
- CVE-2026-95282
- CVE-2026-95373
- CVE-2026-95277
- CVE-2026-95348
- CVE-2026-95335
- CVE-2026-95338
- CVE-2026-95318
- CVE-2026-95286
- CVE-2026-95365
- CVE-2026-95343
- CVE-2026-95280
- CVE-2026-95304
- CVE-2026-95306
- CVE-2026-95299
- CVE-2026-95351
- CVE-2026-95287
- CVE-2026-95366
- CVE-2026-95382
- CVE-2026-95381
- CVE-2026-95331
- CVE-2026-95297
- CVE-2026-95375
- CVE-2026-95302
- CVE-2026-95362
- CVE-2026-95369
- CVE-2026-95376
- CVE-2026-95359
- CVE-2026-95294
- CVE-2026-95337
- CVE-2026-95346
- CVE-2026-95320
- CVE-2026-95317
- CVE-2026-95345
- CVE-2026-95330
- CVE-2026-95370
- CVE-2026-95303
- CVE-2026-95360
- CVE-2026-95295
- CVE-2026-95276
- CVE-2026-95314
- CVE-2026-95371
- CVE-2026-95353
- CVE-2026-95363
- CVE-2026-95341
- CVE-2026-95354
- CVE-2026-95384
- CVE-2026-95336
- CVE-2026-95290
- CVE-2026-95325
- CVE-2026-95275
- CVE-2026-95374
- CVE-2026-95300
- CVE-2026-95321
- CVE-2026-95323
- CVE-2026-95332
- CVE-2026-95312
- CVE-2026-95344
- CVE-2026-95289
- CVE-2026-95347
- CVE-2026-95311
- CVE-2026-95358
- CVE-2026-95333
- CVE-2026-95307
- CVE-2026-95285
- CVE-2026-95278
- CVE-2026-95327
- CVE-2026-95334
- CVE-2026-95308
- CVE-2026-95292
- CVE-2026-95352
- CVE-2026-95279
- CVE-2026-95367
- CVE-2026-95385
- CVE-2026-95368
- CVE-2026-95319
- CVE-2026-95326
- CVE-2026-95309
- CVE-2026-95361
- CVE-2026-95380
- CVE-2026-95342
- CVE-2026-95296
- CVE-2026-95316
- CVE-2026-95328
- CVE-2026-95340
- CVE-2026-95364
- CVE-2026-95305
Frequently Asked Questions
Which deployments are identified as being in scope?
The available information identifies Google Chrome on Mobile. It does not provide affected version numbers or configuration details.
Is there information on temporary mitigations or indicators of compromise?
No workaround, mitigation, exploitation prerequisites, or detection guidance is provided in the available data.