dbcve.org
ChromeWeb browser · Google

CVE-2026-13030

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 149.0.7827.197 or later.
See remediation →
60/100
Remediation priority · Elevated
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
Uninitialized Use in GPU in Google Chrome on Android prior to 149.0.7827.197 allowed a remote attacker to obtain potentially sensitive information from process memory 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 · moderate confidence

An uninitialized use vulnerability in the GPU component of Google Chrome on Android allows a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. The vulnerability exists in versions prior to 149.0.7827.197.

MitigationUpdate Google Chrome on Android to version 149.0.7827.197 or later to patch the uninitialized memory read vulnerability in the GPU renderer.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

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 on Android is installed
    Check the application name and platform. On Android, go to Settings > Apps > Chrome. Verify the app is 'Chrome' (not 'Chrome Beta' or 'Chrome Dev') and the device is running Android OS.
    Affected if The target is not Google Chrome on Android (e.g., desktop Chrome, Chrome iOS, or other browsers are not affected by this specific vulnerability)
  2. Identify installed Chrome version on Android
    Open Chrome on the Android device, navigate to chrome://version, or go to Settings > Apps > Chrome > App info to view the version number.
    Affected if The exact version number cannot be determined or the app is not Google Chrome for Android
  3. Compare version against the affected range
    Compare the installed version number to 149.0.7827.197. Note the full version string including the build number (e.g., 149.0.7827.197).
    Affected if Installed version is less than 149.0.7827.197 (e.g., 148.x.x.x or earlier)
  4. Verify GPU rendering is enabled (default state)
    The GPU renderer is enabled by default in Chrome. No user configuration check is needed - the vulnerability exists in the GPU component itself.
    Affected if GPU rendering has been manually disabled (this would be an uncommon configuration that mitigates the issue)

If the device runs Google Chrome on Android with version less than 149.0.7827.197 and uses default GPU rendering, the environment is affected by this uninitialized memory read vulnerability.

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 on Android to version 149.0.7827.197 or later to patch the uninitialized memory read vulnerability in the GPU renderer.

Recommended fix High confidence

Chrome 149.0.7827.197 or later for Android

  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.197 or later
  5. Alternatively, open Chrome > tap the three-dot menu > Settings > About Chrome > Check for updates
  6. Ensure the update completes before using the browser

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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