ChromeWeb browser · Google
CVE-2026-5276
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 · uneditedInsufficient policy enforcement in WebUSB in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (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 confidenceGoogle Chrome versions prior to 146.0.7680.178 contain insufficient policy enforcement in the WebUSB API, allowing a remote attacker hosting a malicious HTML page to obtain potentially sensitive information from Chrome process memory without user interaction beyond page visit.
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
< 146.0.7680.177CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Chrome versionOpen chrome://version in the Chrome address bar and note the version number listed under 'Google Chrome'Affected if The version number is less than 146.0.7680.177 (for example, 146.0.7680.176 or earlier)
-
Check Chrome release channelOpen chrome://version and look at the 'Profile path' line to confirm this is the standard Chrome browser (not Chromium or Edge)Affected if This is Google Chrome (the vulnerability affects only Google Chrome, not Chromium-based forks)
-
Verify WebUSB API availabilityVisit chrome://settings and search for 'USB' or navigate to Privacy and security > Site Settings > Additional content settings > USB devices to confirm WebUSB is accessibleAffected if WebUSB API is enabled and accessible (this is the default setting; the vulnerability can be triggered when visiting a malicious page)
-
Confirm patch level via help menuClick Help > About Google Chrome and wait for the version check to completeAffected if The displayed version shows a build number lower than 146.0.7680.178
You are affected if your Google Chrome version is below 146.0.7680.177 and the WebUSB API is enabled in your browser settings.
Generated from the published advisory. Verify against your own configuration.
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 · scoped146.0.7680.177
Update Google Chrome to version 146.0.7680.178 or later. For enterprise deployments, use centralized patch management to ensure all instances are updated.
Chrome 146.0.7680.178 or later
- Open Google Chrome
- Click the three-dot menu in the top-right corner
- Navigate to Help > About Google Chrome
- Chrome will check for updates and prompt you to restart if an update is available
- If update available, click 'Update Google Chrome' and restart the browser
- Verify the version is 146.0.7680.178 or later by returning to Help > About Google Chrome
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
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 locallyCheck whether your project pulls in CVE-2026-5276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5276 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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