Skip to main content

Google Chrome CVE-2026-11031

| EUVDEUVD-2026-34480 MEDIUM
Improper Input Validation (CWE-20)
2026-06-04 chrome-cve-admin@google.com GHSA-f56v-w837-cg2p
4.3
CVSS 3.1 · Vendor: google
Share

Severity by source

Vendor (google) PRIMARY
4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
SUSE
MEDIUM
qualitative
Red Hat
8.1 MEDIUM
qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

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

Lifecycle Timeline

4
Analysis Generated
Jun 05, 2026 - 20:43 vuln.today
CVSS changed
Jun 05, 2026 - 20:22 NVD
4.3 (MEDIUM)
CVE Published
Jun 04, 2026 - 23:17 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 04, 2026 - 23:17 nvd
MEDIUM 4.3

DescriptionCVE.org

Insufficient validation of untrusted input in Password Manager in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to perform UI spoofing via malicious network traffic. (Chromium security severity: Medium)

AnalysisAI

UI spoofing in Google Chrome's Password Manager component (versions prior to 149.0.7827.53) allows remote unauthenticated attackers to manipulate browser interface elements via crafted malicious network traffic. The flaw stems from insufficient input validation (CWE-20) in the Password Manager subsystem, enabling an attacker to deceive victims about the legitimacy of password prompts or credential states. No public exploit code or active exploitation has been identified; EPSS at 0.05% (15th percentile) reflects low community-assessed exploitation probability, and the mandatory user interaction requirement prevents automated mass exploitation.

Technical ContextAI

The vulnerability resides in Google Chrome's built-in Password Manager component, which handles credential storage, autofill suggestions, and UI rendering of password-related prompts within the browser. CWE-20 (Improper Input Validation) identifies the root cause as a failure to adequately sanitize or validate attacker-controlled data arriving via network traffic before it is reflected in the Password Manager's user interface. When crafted network content bypasses this validation, Chrome may render misleading UI elements - such as spoofed autofill suggestions or credential prompts - that misrepresent the origin or trustworthiness of password-related interactions. The CVSS vector (AV:N/AC:L) confirms the vulnerability is reachable over the network with low attack complexity. Affected versions span all Chrome desktop builds prior to stable channel release 149.0.7827.53, as confirmed by the ENISA EUVD entry EUVD-2026-34480. No CPE strings were included in available source data; version range is derived from EUVD and the Chrome stable channel advisory.

RemediationAI

The primary remediation is to update Google Chrome to version 149.0.7827.53 or later, the vendor-released patch confirmed by the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome typically applies updates automatically upon browser restart; users and administrators should verify the installed version via chrome://settings/help to confirm the update has been applied. Enterprise administrators using Chrome Browser Cloud Management or group policy should validate fleet-wide version compliance. If immediate patching is not feasible, disabling the Password Manager feature via chrome://settings/passwords eliminates the vulnerable attack surface but removes autofill and credential management functionality - a trade-off that may be acceptable in managed environments with separate password tooling. Given the absence of known active exploitation and the low EPSS score, emergency out-of-band deployment is not warranted; inclusion in the next standard browser maintenance window is appropriate.

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
openSUSE Tumbleweed Fixed

Share

CVE-2026-11031 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy