dbcve.org
ChromeWeb browser · Google

CVE-2026-3542

HIGH · 8.8 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 145.0.7632.159 / 145.0.7632.160 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 WebAssembly in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform out of bounds memory access 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 · moderate confidence

A memory safety vulnerability in Google Chrome's WebAssembly implementation allows a remote attacker to perform out-of-bounds memory access via a specially crafted HTML page. This inappropriate implementation flaw enables the attacker to read or write memory outside the boundaries of allocated WebAssembly buffers.

MitigationUpdate Google Chrome to version 145.0.7632.159 or later to remediate this vulnerability. Users should avoid visiting untrusted 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:< 145.0.7632.159< 145.0.7632.160

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. Locate Chrome installation path
    On Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome
    Affected if Chrome is installed on the system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or from command line run 'google-chrome --version' on Linux/macOS, or right-click chrome.exe > Properties > Details tab on Windows
    Affected if The displayed version number is lower than 145.0.7632.159
  3. Verify WebAssembly is enabled
    In Chrome, go to chrome://flags and search for 'WebAssembly'. Confirm the flag is not disabled (default state is enabled)
    Affected if WebAssembly is enabled (default) - this is required for the vulnerability to be exploitable
  4. Confirm user can be tricked into visiting malicious pages
    Review whether users have unrestricted web browsing capability or can open arbitrary HTML files in Chrome
    Affected if Users can open untrusted HTML pages in Chrome - this is the attack vector

You are affected if Google Chrome version is lower than 145.0.7632.159 and users can be persuaded to open a crafted HTML page in the browser.

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.159 / 145.0.7632.160 or later
Fixed in 145.0.7632.159145.0.7632.160
Interim mitigation

Update Google Chrome to version 145.0.7632.159 or later to remediate this vulnerability. Users should avoid visiting untrusted websites until the browser is updated.

Recommended fix Moderate confidence

Chromium 145.0.7632.159 or later (or the corresponding stable release for your Chromium-based browser that includes this security fix)

  1. 1. Identify the Chromium-based browser in use (Chrome, Edge, Brave, Opera, etc.)
  2. 2. Check the current browser version in the application's Help > About section
  3. 3. If the browser version is below 145.0.7632.159 (or 145.0.7632.160 for the second fixed version), download and install the latest version from the official vendor website
  4. 4. Alternatively, if using Google Chrome, navigate to chrome://settings/help to check for updates and install any available updates
  5. 5. Restart the browser after the update is applied
  6. 6. Verify the version has been updated to 145.0.7632.159 or higher
Caveat Minimal - browser updates typically include backward-compatible changes; however, some enterprise environments may want to test against internal applications first

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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