dbcve.org
ChromeWeb browser · Google

CVE-2026-13032

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 149.0.7827.197 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 8 weeks old

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
Use after free in WebGL in Google Chrome on Android prior to 149.0.7827.197 allowed a remote attacker to potentially perform a sandbox escape 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

This is a use-after-free vulnerability in the WebGL rendering component of Google Chrome on Android. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, potentially allowing a sandbox escape due to the memory corruption. The vulnerability affects versions prior to 149.0.7827.197.

MitigationUpdate Google Chrome for Android to version 149.0.7827.197 or later. Organizations should ensure mobile device management (MDM) or patch management systems deploy the update to affected devices.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome for Android is installed
    Open Android Settings > Apps > Apps, and look for Google Chrome in the installed applications list. Alternatively, check if the Chrome app icon exists on the device home screen or app drawer.
    Affected if Google Chrome for Android is not present on the device - the CVE does not apply
  2. Determine installed Chrome version
    Open the Chrome app, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed at the top (for example, 149.0.7827.197). Alternatively, navigate to chrome://version in the address bar.
    Affected if Unable to determine the installed version - further investigation required
  3. Compare version against affected range
    Take the version number found in the previous step and compare it numerically to 149.0.7827.197. The affected range is any version lower than this (for example, 149.0.7827.196, 148.x.x.x, etc.).
    Affected if Installed version is less than 149.0.7827.197 - the device is vulnerable
  4. Verify WebGL is enabled (affected component)
    In Chrome, go to chrome://flags, search for 'WebGL', and confirm the WebGL rendering feature is enabled. WebGL is typically enabled by default on Chrome for Android.
    Affected if WebGL is enabled and version is below 149.0.7827.197 - the specific attack surface for this CVE is present

A user is affected if Google Chrome for Android is installed with a version number lower than 149.0.7827.197 and WebGL rendering is enabled on the device.

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

Update Google Chrome for Android to version 149.0.7827.197 or later. Organizations should ensure mobile device management (MDM) or patch management systems deploy the update to affected devices.

Recommended fix High confidence

Chrome for Android 149.0.7827.197 or later

  1. Open Google Play Store on the Android device
  2. Search for "Google Chrome" or locate it in your app list
  3. Tap on Chrome and select "Update" to install the latest version
  4. Alternatively, open Chrome, tap the three-dot menu, go to Settings > Help & About > Google Chrome to check for updates
  5. Ensure the updated version is 149.0.7827.197 or later
  6. Restart Chrome after the update completes

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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