VulnerabilityPublished 11 Mar 2026Updated 13 Mar 2026

CVE-2026-3927: Google Chrome · Incorrect Security UI

Affects Google ChromeSource CVE Database V5

Compare

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

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

4.3Medium

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

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

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 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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 Chrome and google/chrome to 146.0.7680.71.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=146.0.7680.71 <146.0.7680.71	Fixed in 146.0.7680.71
Googlegoogle/chrome`pkg:deb/google/chrome`Other threats	Affected <146.0.7680.71	Fixed in 146.0.7680.71

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-3927, organizations should: 1) Ensure all Chrome installations are updated to version 146.0.7680.71 or later, where the vulnerability is fixed. 2) Implement browser update policies that enforce timely patching, especially for users with elevated privileges or access to sensitive data. 3) Educate users about the risks of interacting with untrusted Picture-in-Picture content and encourage vigilance against suspicious UI elements or prompts. 4) Employ endpoint security solutions that can detect and block malicious web content or scripts attempting to exploit UI spoofing vulnerabilities. 5) Consider restricting or monitoring the use of Picture-in-Picture features in high-risk environments if feasible. These steps go beyond generic patching by emphasizing user awareness and controlled feature usage.

Description

CVE-2026-3927 is a medium-severity vulnerability in Google Chrome's Picture-in-Picture (PiP) feature prior to version 146.0.7680.71. It allows a remote attacker to perform UI spoofing by crafting a malicious HTML page that misleads users about the security state of the browser interface. The flaw does not impact confidentiality or availability but can affect integrity by tricking users into believing they are interacting with legitimate UI elements. Exploitation requires user interaction to trigger the spoofed UI. No known exploits are currently in the wild. The vulnerability is addressed in Chrome version 146.0.

Impact

The primary impact of CVE-2026-3927 is on user trust and integrity of the browser interface. By spoofing security UI elements in the Picture-in-Picture mode, attackers can deceive users into performing unsafe actions, such as entering credentials or approving permissions under false pretenses. While the vulnerability does not directly compromise data confidentiality or system availability, successful exploitation can facilitate phishing, social engineering, or further exploitation by tricking users. Organizations relying heavily on Chrome for web access, especially those with users who frequently use multimedia features like PiP, may face increased risk of targeted phishing attacks. The medium severity indicates moderate risk, but the requirement for user interaction and absence of privilege escalation limit the scope of impact. Nonetheless, this vulnerability can be a stepping stone in multi-stage attacks.

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 20 Mar 2026, 02:42 UTC

WeaknessesCWE-451

Technical details

References

Community reviews

Related threats