dbcve.org
ChromeWeb browser · Google

CVE-2026-8006

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
61/100
Remediation priority · Elevated
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 DevTools in Google Chrome prior to 148.0.7778.96 allowed an attacker who convinced a user to install a malicious extension to perform UI spoofing via a crafted Chrome Extension. (Chromium security severity: Low)

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 · moderate confidence

Insufficient policy enforcement in Chrome DevTools allowed a maliciously crafted Chrome Extension to perform UI spoofing. The vulnerability exists in Chrome versions prior to 148.0.7778.96 and requires a user to install a malicious extension for exploitation.

MitigationUpdate Chrome to version 148.0.7778.96 or later and enforce organizational policies restricting extension installation to trusted sources from the Chrome Web Store.

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:< 148.0.7778.96

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
Low
Integrity
None
Availability
Low

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

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 the installed Chrome version
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome. The version number is displayed on this page.
    Affected if The version shown is earlier than 148.0.7778.96 (for example, 148.0.7778.0, 147.x.x.x, etc.)
  2. Verify if extension installation policies are enforced
    Open Chrome and navigate to chrome://extensions. Look for the 'Developer mode' toggle and check if there is a managed-by-organizational-policy indicator on the extensions page. Alternatively, run gpedit.msc on Windows and check Computer Configuration > Administrative Templates > Google Chrome > Extensions for 'Extension installation settings'.
    Affected if Extensions can be installed freely without organizational policy restrictions, meaning users can enable Developer mode and load unpacked extensions.
  3. Review installed extensions for unknown or untrusted sources
    In Chrome, go to chrome://extensions and examine the list of installed extensions. Check the source column or details for each extension to identify any that are not from the Chrome Web Store or not approved by your organization.
    Affected if Any extension is present that was not obtained from the Chrome Web Store or was installed without organizational approval.
  4. Check for DevTools-specific extension access policies
    Navigate to chrome://policy and look for any policies related to DevTools or extension access to DevTools panels. Search for policies containing 'DevTools' or 'extension' keywords in the policy viewer.
    Affected if No policies are configured to restrict extensions from accessing or manipulating DevTools UI elements.

You are affected if your Chrome version is earlier than 148.0.7778.96 AND users can install extensions (especially untrusted or non-Web Store extensions) without organizational policy controls in place.

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 148.0.7778.96 or later
Fixed in 148.0.7778.96
Interim mitigation

Update Chrome to version 148.0.7778.96 or later and enforce organizational policies restricting extension installation to trusted sources from the Chrome Web Store.

Recommended fix High confidence

Chrome 148.0.7778.96 or later

  1. Open Chrome and navigate to Help > About Google Chrome to check the current version
  2. If the version is lower than 148.0.7778.96, click 'Update Google Chrome' to download and install the latest version
  3. Restart Chrome after the update completes
  4. Alternatively, download the latest Chrome version directly from the official Chrome download page

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8006 — 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-8006 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