CVE-2026-18003: Google Chrome for iOS UI spoofing via crafted HTML page

CVE-2026-18003 · Severity: info · Published 2026-07-30

A vulnerability in Google Chrome for iOS could allow a malicious website to spoof parts of the browser's user interface. This could be used to trick users into believing they are on a legitimate site or interacting with a trusted browser element, potentially leading to phishing or the disclosure of sensitive information. Users should update to the latest version of Chrome on their iOS devices to mitigate this risk.

Technologies: Google Chrome for iOS. Vendors: Google.

Quick answers

Is CVE-2026-18003 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-18003 being exploited in the wild.
How severe is CVE-2026-18003?
Informational severity, published 30 July 2026.
Which products and versions are affected?
Google Chrome for iOS prior to 151.0.7922.72.
Is there a fix for CVE-2026-18003?
A patch was published on 2026-07-29. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-18003 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-18003?
Check whether you run Google Chrome for iOS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A UI spoofing vulnerability exists in Google Chrome for iOS due to an inappropriate implementation within the browser's interface handling. A remote attacker can exploit this by enticing a user to visit a specially crafted HTML page. Successful exploitation allows the attacker to misrepresent or overlap browser UI elements, which can be leveraged for phishing attacks. The issue is addressed in version 151.0.7922.72. Chromium has assigned this a security severity of Low.

Affected products

  • Google Chrome for iOS prior to 151.0.7922.72

Timeline

  • 2026-07-29: disclosed
  • 2026-07-29: patched
  • 2026-07-30: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.