dbcve.org
ChromeWeb browser · Google

CVE-2025-12725

HIGH · 8.8 CVSS v3.1 Published 2025-11-10
Fix available
A fix is available. Upgrade to 142.0.7444.134 / 142.0.7444.135 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
Out of bounds read in WebGPU in Google Chrome on Android prior to 142.0.7444.137 allowed a remote attacker to perform an out of bounds memory write 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

Out of bounds memory write vulnerability in WebGPU implementation in Google Chrome on Android prior to version 142.0.7444.137 allows remote attackers to execute arbitrary memory operations via a specially crafted HTML page.

MitigationUpdate Google Chrome for Android to version 142.0.7444.137 or later; enforce automatic updates via mobile device management (MDM) to prevent regression.

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:< 142.0.7444.137< 142.0.7444.134< 142.0.7444.135

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 for Android is installed
    Check the device for Google Chrome browser - look for the Chrome app icon (circle with blue/red/yellow/green logo) in the app drawer or settings under Apps. This vulnerability only affects Chrome on Android, not iOS or desktop.
    Affected if Chrome for Android is not installed - this CVE does not apply to other browsers or platforms.
  2. Find installed Chrome version on Android
    Open Chrome app, tap the three-dot menu > Settings > About Chrome. The version number is displayed at the top (for example, 142.0.7444.137).
    Affected if The version shown is below 142.0.7444.137 (for example, 141.x.x.x or earlier).
  3. Check WebGPU feature status
    In Chrome on Android, type chrome://flags in the address bar, then search for 'WebGPU' in the flags search box. Check if WebGPU is enabled or set to Default.
    Affected if WebGPU is enabled or set to Default - the vulnerability exists in the WebGPU implementation, so this feature must be active for exploitation.
  4. Review recent browsing behavior
    Check Chrome history (tap three-dot menu > History) for any suspicious or unfamiliar websites visited, particularly around the time frame this CVE was publicly disclosed.
    Affected if User has visited untrusted or crafted HTML pages - the attack requires tricking users into visiting a malicious page.

A user is affected if they have Google Chrome for Android version below 142.0.7444.137 with WebGPU enabled and potential exposure to malicious 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 142.0.7444.134 / 142.0.7444.135 / 142.0.7444.137 or later
Fixed in 142.0.7444.134142.0.7444.135142.0.7444.137
Interim mitigation

Update Google Chrome for Android to version 142.0.7444.137 or later; enforce automatic updates via mobile device management (MDM) to prevent regression.

Recommended fix High confidence

Chrome for Android 142.0.7444.137 or later (ensure you're on the latest stable release)

  1. Open the Google Play Store on your Android device
  2. Search for "Google Chrome" or locate it in your installed apps
  3. Tap "Update" to install the latest version of Chrome
  4. Alternatively, ensure Auto-update is enabled in Play Store settings to receive future security patches automatically
  5. 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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,064.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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