ChromeWeb browser · Google
CVE-2026-13028
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 · uneditedUse 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 confidenceUse-after-free vulnerability in WebGL (graphics rendering) component of Google Chrome for Android allows a remote attacker to potentially escape the sandbox and execute arbitrary code via a maliciously crafted HTML page. The vulnerability is fixed in Chrome for Android version 149.0.7827.197 and later.
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
< 149.0.7827.197CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Chrome for Android installationCheck if Google Chrome is installed on the Android device via Settings > Apps > Google Chrome, or use an MDM/EMM inventory tool to query installed packages.Affected if Google Chrome for Android is not installed on the device.
-
Determine the installed Chrome versionOpen Google Chrome, navigate to chrome://version, or check the app version under Settings > Apps > Google Chrome > App info. Note the version number displayed.Affected if The displayed version number is lower than 149.0.7827.197.
-
Confirm WebGL is accessibleOpen a WebGL-enabled page in Chrome (e.g., visit a WebGL demo site), or verify WebGL is not disabled via chrome://flags/#disable-webgl.Affected if WebGL is enabled and functional on the device.
-
Compare version against CVE thresholdReview the full version string obtained from chrome://version or the app info screen, comparing it numerically against 149.0.7827.197.Affected if The version is below 149.0.7827.197 (e.g., 149.0.7827.196 or earlier).
The device is affected if Google Chrome for Android is installed with a version lower than 149.0.7827.197 and WebGL is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped149.0.7827.197
Update Google Chrome for Android to version 149.0.7827.197 or later. Organizations should ensure mobile devices receive browser updates through MDM or enterprise mobility policies.
Chrome 149.0.7827.197 or later (Android)
- Open the Google Play Store app on your Android device
- Search for 'Google Chrome' or locate it in your installed applications
- Tap the 'Update' button if an update is available, or verify that you have version 149.0.7827.197 or later
- Alternatively, open Chrome and go to Settings > Help > About Chrome to check for and apply updates
- 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
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13028 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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