Cyber Resilience

CVE-2026-3927

Google Chrome ≤ 146.0.7680.71

Published
11 March 2026
Modified
13 March 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS Score 0.0018 7th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-3927 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Spearphishing Link (T1566.002); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and SC-18 (Mobile Code) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Incorrect security UI in PictureInPicture in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1566.002 Spearphishing Link Initial Access
Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems.
T1204.001 Malicious Link Execution
An adversary may rely upon a user clicking a malicious link in order to gain execution.
Why these techniques?

UI spoofing via crafted HTML page directly enables deceptive links or content that trick users into execution or interaction.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-11300Same product: Apple Macos
CVE-2026-11294Same product: Apple Macos
CVE-2026-3937Same product: Apple Macos
CVE-2026-3935Same product: Apple Macos
CVE-2026-3925Same product: Apple Macos
CVE-2026-0904Same product: Apple Macos
CVE-2026-7935Same product: Apple Macos
CVE-2026-0906Same product: Apple Macos
CVE-2026-8561Same product: Apple Macos
CVE-2026-5895Same product: Apple Macos

Affected Assets

google
chrome
≤ 146.0.7680.71

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SI-7 Software, Firmware, and Information Integrity
  • SC-18 Mobile Code
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires timely patching of Chrome to remediate the incorrect Picture-in-Picture security UI that enables spoofing.

prevent

Verifies integrity of browser software and rendered content, reducing the chance a crafted page can successfully spoof the PiP interface.

SC-18 Mobile Code partial match
prevent

Restricts execution and privileges of mobile code (HTML/JS) that a remote attacker would use to trigger the UI spoofing flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly address design and implementation of accurate, non-spoofable UI elements.

PR.AT-01 partial match
prevents

User awareness training helps people recognize and avoid harm from UI misrepresentation such as phishing, but does not prevent the flaw itself.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect UI misrepresentation vulnerabilities before deployment.

prevents

Security awareness training can teach users to recognize UI misrepresentation and phishing attempts.

mitigates

Web filtering can block known phishing sites that exploit UI misrepresentation.

prevents

Secure development lifecycle includes UI/UX security requirements that can prevent misrepresentation of critical information.

prevents

Application security requirements can mandate proper display and validation of critical information in the UI.

prevents

Secure coding practices can prevent UI flaws that obscure or spoof critical information.

References