VulnerabilityPublished 30 Jul 2026

CVE-2026-17941: Google Chrome · Inappropriate Implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 151.0.7922.72 when convenient.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 151.0.7922.72

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 151.0.7922.72.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=151.0.7922.72 <151.0.7922.72	Fixed in 151.0.7922.72

AI-suggested

Users should update Google Chrome for iOS to version 151.0.7922.72 or later once available. Until then, users should exercise caution when interacting with suspicious web pages and verify URLs carefully.

Description

CVE-2026-17941 is a vulnerability in Google Chrome for iOS versions prior to 151.0.7922.72 that allows a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. The issue is classified with a low security severity by Chromium and has a CVSS score of 4.3, indicating medium severity. This vulnerability could mislead users about the actual URL they are visiting, potentially facilitating phishing or other social engineering attacks. No known exploits are reported in the wild.

Impact

The vulnerability allows remote attackers to spoof the URL bar content in Chrome for iOS, potentially misleading users about the website they are visiting. This can facilitate phishing attacks or other social engineering exploits by making malicious sites appear legitimate. There is no impact on confidentiality or availability. No known active exploitation has been reported.

Summary

An inappropriate implementation in Google Chrome for iOS prior to version 151.0.7922.72 allows remote attackers to spoof the Omnibox (URL bar) content by using a crafted HTML page. This vulnerability is tracked as CVE-2026-17941 and is associated with CWE-451 (Incorrect Expression of URL). The CVSS 3.1 base score is 4.3, reflecting a medium severity with no confidentiality or availability impact but with integrity impact due to the spoofing capability. The vulnerability requires no privileges and user interaction is required to trigger the spoofing. The vendor has published a stable channel update announcement but does not explicitly confirm the patch status in the advisory linked.

CWE-451User Interface (UI) Misrepresentation of Critical Information (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.
Implementation · Input Validation
Perform data validation (e.g. syntax, length, etc.) before interpreting the data.
Architecture and Design · Output Encoding
Create a strategy for presenting information, and plan for how to display unusual characters.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Spear Phishing (opens in a new tab)
Mobile Phishing (opens in a new tab)
Phishing (opens in a new tab)
Resource Location Spoofing (opens in a new tab)
Action Spoofing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2026, 17:11 UTC

WeaknessesCWE-451

Technical details

References

Community reviews

Related threats