dbcve.org
ChromeWeb browser · Google

CVE-2026-12030

HIGH · 8.3 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 149.0.7827.115 or later.
See remediation →
90/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 write in GPU in Google Chrome on Android prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process 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

This is an out-of-bounds write vulnerability in the GPU component of Google Chrome for Android. An attacker who has already compromised the renderer process can exploit this flaw via a crafted HTML page to potentially escape Chrome's sandbox isolation. The vulnerability affects versions prior to 149.0.7827.115.

MitigationUpdate Google Chrome for Android to version 149.0.7827.115 or later to remediate this vulnerability. Organizations with managed devices should verify all endpoints have applied the patch.

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.115

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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
    Check device settings under Apps > Chrome, or run 'pm list packages | grep chrome' via ADB shell to verify the Chrome package is present
    Affected if Google Chrome for Android package is found on the device
  2. Retrieve the installed Chrome version
    Navigate to Chrome Settings > Help & Feedback > About Chrome, or run 'dumpsys package com.android.chrome | grep versionName' via ADB shell
    Affected if Unable to retrieve version information from the Chrome installation
  3. Compare version against the vulnerable range
    Compare the retrieved version code to 149.0.7827.115 using semantic version comparison
    Affected if The installed version is lower than 149.0.7827.115 (for example, 149.0.7827.100 or earlier)
  4. Verify renderer process exposure (context check)
    Confirm the device runs Chrome with full renderer capabilities enabled, which is the default state; no configuration change needed for exploitation
    Affected if Chrome is actively used with renderer process enabled, which is the standard configuration

A user is affected if Google Chrome for Android is installed with a version lower than 149.0.7827.115 and the browser is actively rendering web content.

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.115 or later
Fixed in 149.0.7827.115
Interim mitigation

Update Google Chrome for Android to version 149.0.7827.115 or later to remediate this vulnerability. Organizations with managed devices should verify all endpoints have applied the patch.

Recommended fix High confidence

Chrome 149.0.7827.115 or later

  1. Open Google Play Store on the Android device
  2. Search for "Google Chrome" in the Play Store
  3. Tap on Google Chrome from the search results
  4. Tap the "Update" button to install version 149.0.7827.115 or later
  5. Alternatively, ensure Chrome auto-updates are enabled by going to Play Store > Settings > Auto-update apps > Auto-update apps at any time
  6. After updating, verify the version by opening Chrome > Settings > About Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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