dbcve.org
ChromeWeb browser · Google

CVE-2026-7354

HIGH · 8.8 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 147.0.7727.138 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
Out of bounds read and write in Angle in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to potentially perform a sandbox escape 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

Out of bounds memory read/write vulnerability in Google's Angle graphics layer (OpenGL ES translation backend) in Chrome browsers prior to version 147.0.7727.138. A remote attacker can exploit this via a crafted HTML page to potentially escape the browser's sandbox and execute arbitrary code with elevated privileges.

MitigationUpdate Google Chrome to version 147.0.7727.138 or later to apply the security patch. Organizations should prioritize updating browser installations given the high CVSS score and sandbox escape potential.

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

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. Verify Google Chrome is installed
    Check for Chrome installation in typical locations: Windows (C:\Program Files\Google\Chrome\Application\chrome.exe), macOS (/Applications/Google Chrome.app), or Linux (/usr/bin/google-chrome or /opt/google/chrome/google-chrome). Use file system enumeration or package manager queries.
    Affected if Google Chrome browser is present on the endpoint.
  2. Retrieve installed Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' from command line on Linux/Mac, or check 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome' registry key on Windows.
    Affected if A version number can be retrieved from the Chrome installation.
  3. Compare version against affected range
    Parse the retrieved version number (e.g., 147.0.7727.138) and compare numerically against 147.0.7727.138. Any version with major version less than 147, or major=147 with minor less than 7727, or major=147/minor=7727 with build less than 138, is affected.
    Affected if Installed version is less than 147.0.7727.138 (e.g., 146.x.x.x, 147.0.7727.100, etc.).

The environment is affected if Google Chrome is installed and its version number is lower than 147.0.7727.138.

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

Update Google Chrome to version 147.0.7727.138 or later to apply the security patch. Organizations should prioritize updating browser installations given the high CVSS score and sandbox escape potential.

Recommended fix High confidence

Chrome 147.0.7727.138

  1. Open Chrome browser and navigate to Settings > Help > About Google Chrome
  2. Chrome will automatically check for available updates
  3. If version 147.0.7727.138 or later is available, click 'Update Google Chrome'
  4. Restart the browser to complete the installation of the security update
  5. Verify the version by returning to About Chrome and confirming the installed version is 147.0.7727.138 or later
  6. For enterprise-managed devices, consult your IT administrator if automatic updates are disabled

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-7354 — 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-7354 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