dbcve.org
ChromeWeb browser · Google

CVE-2026-0628

HIGH · 8.8 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 143.0.7499.192 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Insufficient policy enforcement in Chrome's WebView tag allows a malicious extension to inject scripts or HTML into privileged pages. The attacker must convince the user to install a crafted malicious extension, which then exploits the WebView component to escape its security boundaries.

MitigationUpdate Google Chrome to version 143.0.7499.192 or later. Users should be cautioned against installing extensions from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 143.0.7499.192

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://settings/help or click Help > About Google Chrome to view the current version number
    Affected if The displayed version is lower than 143.0.7499.192
  2. Review installed extensions
    Navigate to chrome://extensions/ and review all installed extensions, especially those from untrusted sources or that you did not intentionally install
    Affected if Any extension you did not trust or recognize is installed, as the vulnerability requires a malicious extension to exploit the WebView tag
  3. Verify extension permissions
    For each extension in chrome://extensions/, click Details and review permissions - look for suspicious permissions or extensions requesting excessive access
    Affected if Extensions have broad permissions that could be leveraged to abuse the WebView tag vulnerability
  4. Check for unknown extensions
    Look for extensions you did not explicitly install or that appeared recently without your action
    Affected if Unknown or unexpected extensions are present in the browser

You are affected if your Chrome version is below 143.0.7499.192 AND you have any untrusted or malicious extension installed, as both conditions are required for this vulnerability to be exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 143.0.7499.192 or later
Fixed in 143.0.7499.192
Interim mitigation

Update Google Chrome to version 143.0.7499.192 or later. Users should be cautioned against installing extensions from untrusted sources.

Recommended fix High confidence

Chrome 143.0.7499.192 or later

  1. Open Chrome and navigate to Settings > About Chrome to check your current version number
  2. Download Chrome version 143.0.7499.192 or later from the official Chrome download page (chrome.com)
  3. Install the updated version by running the installer or allowing Chrome's automatic update to complete
  4. Restart Chrome to ensure the update is fully applied
  5. Verify the installed version is 143.0.7499.192 or higher via Settings > About Chrome
Caveat Chrome typically auto-updates with minimal user intervention; ensure extensions are compatible with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA2.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0628 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data