ChromeWeb browser · Google
CVE-2025-1426
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 · uneditedHeap buffer overflow in GPU in Google Chrome on Android prior to 133.0.6943.126 allowed a remote attacker to potentially exploit heap corruption 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 confidenceHeap buffer overflow vulnerability in the GPU component of Google Chrome on Android allows a remote attacker to exploit heap corruption via a crafted HTML page, potentially leading to arbitrary code execution.
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
< 133.0.6943.126CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Chrome on Android is installedCheck if Google Chrome browser is installed on the Android device by looking in the app drawer or using a package manager command like 'pm list packages | grep chrome'Affected if Google Chrome is not installed on the Android device, this CVE does not apply
-
Identify installed Chrome version on AndroidOpen Google Chrome, tap the three-dot menu, go to Settings > About Chrome to view the version number, or navigate to chrome://version in the address barAffected if The displayed version number is less than 133.0.6943.126 (for example, 133.0.6943.125 or earlier)
-
Verify GPU feature is enabledThe vulnerability exists in the GPU component. Check if hardware acceleration is enabled by navigating to chrome://flags/#enable-gpu-rasterization or chrome://gpu in Chrome on Android. By default, GPU hardware acceleration is typically enabled on mobile Chrome.Affected if Hardware acceleration and GPU rendering features are enabled (this is the default state; disabling these features may mitigate but the detection is simply confirming the attack surface exists)
A user is affected if Google Chrome for Android is installed with a version number lower than 133.0.6943.126 and GPU/hardware acceleration features are enabled (the default configuration).
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 · scoped133.0.6943.126
Update Google Chrome on Android to version 133.0.6943.126 or later to patch the vulnerability.
133.0.6943.126
- Open the Google Play Store app on your Android device
- Search for "Google Chrome" or find it in your installed apps
- Tap on Google Chrome in the search results
- If an update is available, tap the "Update" button to install version 133.0.6943.126 or later
- Alternatively, open Chrome > tap the three dots menu > tap Help & Feedback > tap About Chrome to check for and apply updates
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1426 — 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-2025-1426 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