dbcve.org
ChromeWeb browser · Google

CVE-2026-3537

HIGH · 8.8 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 145.0.7632.159 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
Object lifecycle issue in PowerVR in Google Chrome on Android prior to 145.0.7632.159 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

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

A memory management vulnerability in the PowerVR GPU driver within Google Chrome for Android allows a remote attacker to corrupt heap memory via a malicious HTML page. The issue stems from improper object lifecycle handling, leading to use-after-free or similar memory corruption that can be exploited for code execution.

MitigationUpdate Google Chrome for Android to version 145.0.7632.159 or later to patch the PowerVR driver vulnerability.

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

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. Confirm Chrome on Android is installed
    Open Chrome on the Android device and navigate to chrome://version to see if Chrome browser is running on Android
    Affected if Not Chrome browser on Android platform - this vulnerability only affects Chrome on Android, not other platforms
  2. Check installed Chrome version on Android
    On the Android device, open Chrome, tap the three-dot menu, go to Settings > About Chrome to view the version number
    Affected if Cannot determine version - version information unavailable
  3. Compare version against affected range
    Compare the displayed version number to 145.0.7632.159 - any version lower than 145.0.7632.159 is within the affected range
    Affected if Installed version is 145.0.7632.159 or higher - these versions are patched
  4. Verify PowerVR graphics is present
    Check device specifications - PowerVR graphics GPU is typically found on devices with certain ARM Mali or PowerVR chipsets; this vulnerability exists in the PowerVR graphics component
    Affected if Device does not use PowerVR graphics - the specific component containing the flaw is not present

User is affected if running Google Chrome on Android with version lower than 145.0.7632.159 on a device with PowerVR graphics component.

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

Update Google Chrome for Android to version 145.0.7632.159 or later to patch the PowerVR driver vulnerability.

Recommended fix High confidence

Chrome for Android version 145.0.7632.159

  1. Open Google Play Store on the Android device
  2. Search for "Google Chrome" in the app store
  3. If an update is available, tap the "Update" button to install version 145.0.7632.159 or later
  4. Wait for the update to download and install completely
  5. Restart the Chrome browser if it was open during the update
  6. Alternatively, enable automatic app updates in Google Play Store settings to ensure future security updates are applied automatically

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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