dbcve.org
ChromeWeb browser · Google

CVE-2026-4677

HIGH · 8.8 CVSS v3.1 Published 2026-03-24
Fix available
A fix is available. Upgrade to 146.0.7680.164 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
Inappropriate implementation in WebAudio in Google Chrome prior to 146.0.7680.165 allowed a remote attacker to perform an out of bounds memory read 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 confidence

An out-of-bounds memory read vulnerability exists in Google Chrome's WebAudio implementation prior to version 146.0.7680.165. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially allowing unauthorized disclosure of sensitive memory contents.

MitigationUpdate Google Chrome to version 146.0.7680.165 or later. Avoid visiting untrusted or unknown websites until the browser is updated.

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

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 Google Chrome installed version
    Navigate to chrome://settings/help or use 'About Google Chrome' in the Chrome menu to display the current version number
    Affected if The displayed version is less than 146.0.7680.164 (for example, 146.0.7680.163 or earlier)
  2. Verify WebAudio is enabled
    Navigate to chrome://settings/content in the browser address bar and locate the WebAudio setting under Content settings, or check chrome://flags for any WebAudio-related experiments
    Affected if WebAudio is enabled (this is the default state; the vulnerability requires WebAudio to be active)

You are affected if your Google Chrome version is 146.0.7680.163 or earlier and WebAudio is enabled (default setting).

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

Update Google Chrome to version 146.0.7680.165 or later. Avoid visiting untrusted or unknown websites until the browser is updated.

Recommended fix High confidence

Chrome 146.0.7680.165 or later

  1. Open Google Chrome on your system
  2. Click the three-dot menu icon in the top-right corner of the browser window
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. The browser will automatically check for and download the latest version (146.0.7680.165 or later)
  6. Click 'Relaunch' to complete the installation of the security update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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