Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0628: Insufficient policy enforcement in Google Chrome

0
High
VulnerabilityCVE-2026-0628cvecve-2026-0628
Published: Tue Jan 06 2026 (01/06/2026, 23:57:00 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Insufficient policy enforcement in WebView tag in Google Chrome prior to 143.0.7499.192 allowed an attacker who convinced a user to install a malicious extension to inject scripts or HTML into a privileged page via a crafted Chrome Extension. (Chromium security severity: High)

AI-Powered Analysis

AILast updated: 01/14/2026, 01:31:31 UTC

Technical Analysis

CVE-2026-0628 is a vulnerability identified in Google Chrome versions prior to 143.0.7499.192, specifically related to insufficient policy enforcement in the WebView tag. The WebView tag is used to embed web content within Chrome extensions or applications. Due to improper enforcement of security policies, an attacker can craft a malicious Chrome extension that, once installed by a user, can inject arbitrary scripts or HTML into privileged pages within the browser context. This injection capability can lead to a full compromise of the browser environment, allowing the attacker to manipulate content, steal sensitive information, or disrupt browser functionality. The attack vector requires social engineering to convince users to install the malicious extension, but no prior privileges or authentication are necessary. The vulnerability is categorized under CWE-862 (Missing Authorization), indicating that the enforcement of access control policies is flawed. The CVSS v3.1 score of 8.8 reflects high impact on confidentiality, integrity, and availability, with low attack complexity and no privileges required, but user interaction is necessary. Although no known exploits have been reported in the wild, the potential for exploitation is significant given Chrome's widespread use. The lack of patch links in the provided data suggests that the fix is either integrated into version 143.0.7499.192 or forthcoming, emphasizing the importance of timely updates.

Potential Impact

For European organizations, this vulnerability poses a substantial risk due to the widespread use of Google Chrome as a primary web browser in corporate and governmental environments. Successful exploitation can lead to unauthorized access to sensitive data, manipulation of web content, and disruption of browser-based workflows. This can result in data breaches, loss of intellectual property, and operational downtime. Organizations relying on Chrome extensions for business-critical functions are particularly vulnerable, as malicious extensions could bypass intended security controls. The requirement for user interaction (installing an extension) means that phishing or social engineering campaigns could be leveraged to exploit this vulnerability. Given the high CVSS score and the potential for privilege escalation within the browser, the threat could facilitate further lateral movement or persistent access within enterprise networks. The impact extends to compliance risks under GDPR if personal data is compromised. Additionally, sectors such as finance, healthcare, and public administration in Europe, which heavily depend on secure web browsing, face elevated risks.

Mitigation Recommendations

1. Immediately update all Google Chrome installations to version 143.0.7499.192 or later, where the vulnerability is addressed. 2. Enforce strict enterprise policies to control and whitelist allowed Chrome extensions, preventing unauthorized or unverified extensions from being installed. 3. Implement user awareness training focused on the risks of installing untrusted browser extensions and recognizing social engineering attempts. 4. Utilize endpoint security solutions capable of monitoring and blocking suspicious extension behaviors or unauthorized script injections. 5. Regularly audit installed extensions across organizational devices to detect and remove any potentially malicious or unnecessary extensions. 6. Employ network-level controls to monitor and restrict communications initiated by browser extensions to untrusted external servers. 7. Consider deploying browser isolation technologies for high-risk user groups to contain potential exploitation. 8. Maintain up-to-date incident response plans that include scenarios involving browser-based compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-01-05T23:32:30.339Z
Cvss Version
null
State
PUBLISHED

Threat ID: 695da30cee4c93a4aaa68c92

Added to database: 1/7/2026, 12:04:28 AM

Last enriched: 1/14/2026, 1:31:31 AM

Last updated: 2/7/2026, 6:30:29 AM

Views: 1361

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats