dbcve.org
ChromeWeb browser · Google

CVE-2026-3063

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-23
Fix available
A fix is available. Upgrade to 145.0.7632.116 / 145.0.7632.117 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
Inappropriate implementation in DevTools in Google Chrome prior to 145.0.7632.116 allowed an attacker who convinced a user to install a malicious extension to inject scripts or HTML into a privileged page via DevTools. (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

This is a logic flaw in Chrome's DevTools that allows a malicious extension (once installed by the user) to inject scripts or HTML into privileged internal pages like chrome://settings. The vulnerability stems from insufficient validation in how DevTools handles extension context when accessing privileged pages.

MitigationUpdate Google Chrome to version 145.0.7632.116 or later to receive the patch. Additionally, enforce policies that restrict extension installation to trusted sources from the Chrome Web Store only.

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:< 145.0.7632.116< 145.0.7632.117

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

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

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://version in the browser or run 'google-chrome --version' from command line. The version number appears next to 'Google Chrome' or is output by the command.
    Affected if The version is below 145.0.7632.116 or 145.0.7632.117 (the two affected version ranges). Compare your version to these values.
  2. Identify installed browser extensions
    Navigate to chrome://extensions or click the puzzle piece icon in Chrome toolbar. Review the list of installed extensions and note their sources (either 'Chrome Web Store' or 'Developer mode' / unpacked).
    Affected if Any extension is installed from a source other than the Chrome Web Store, or any untrusted extension exists, as the vulnerability requires a malicious extension to be installed by the user.
  3. Verify DevTools availability
    Open DevTools by pressing F12, Ctrl+Shift+I, or right-clicking and selecting 'Inspect'. Confirm the DevTools window opens successfully.
    Affected if DevTools is functional and accessible, which is required for the attack vector to function.
  4. Confirm privileged page access from extensions
    This check requires examining whether extensions have permission to access chrome:// URLs. Review extension permissions in chrome://extensions by clicking 'Details' on each extension and checking for chrome:// URLs in the permissions list.
    Affected if Any installed extension has permissions to access chrome://settings or other internal privileged pages.

A user is affected if their Chrome version is below 145.0.7632.116/145.0.7632.117 AND they have a potentially untrusted extension installed that could leverage DevTools to access privileged internal pages.

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 145.0.7632.116 / 145.0.7632.117 or later
Fixed in 145.0.7632.116145.0.7632.117
Interim mitigation

Update Google Chrome to version 145.0.7632.116 or later to receive the patch. Additionally, enforce policies that restrict extension installation to trusted sources from the Chrome Web Store only.

Recommended fix Moderate confidence

Chrome 145.0.7632.117 or later

  1. Verify the current Chrome version by navigating to chrome://settings/help
  2. Download Chrome version 145.0.7632.117 or later from the official Chrome release channel (chromereleases.googleblog.com)
  3. Restart Chrome to complete the update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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