dbcve.org
ChromeWeb browser · Google

CVE-2025-3068

HIGH · 8.8 CVSS v3.1 Published 2025-04-02
Fix available
A fix is available. Upgrade to 135.0.7049.52 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
Inappropriate implementation in Intents in Google Chrome on Android prior to 135.0.7049.52 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)

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

This vulnerability in Google Chrome on Android stems from an inappropriate implementation of Android Intents, which are the message-passing mechanism for Android components. A remote attacker can exploit this by crafting a malicious HTML page that triggers privileged Android intents, potentially elevating the attacker's capabilities beyond what a web page should normally have access to.

MitigationUpdate Google Chrome on Android to version 135.0.7049.52 or later. Organizations should use MDM solutions to verify and enforce Chrome updates across managed devices.

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:< 135.0.7049.52

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. Identify Chrome on Android
    Check if Google Chrome is installed on an Android device. This vulnerability only affects the Chrome browser when running on Android operating systems, not on desktop platforms.
    Affected if Chrome browser is installed and running on an Android device or emulator.
  2. Determine Chrome version on Android
    Open Chrome on the Android device, navigate to chrome://version, or go to Settings > Apps > Chrome to view the installed version number.
    Affected if Unable to determine version or version information is not displayed.
  3. Compare against affected version range
    Review the version number found in the previous step. Compare it numerically to the affected range: any version less than 135.0.7049.52 is vulnerable.
    Affected if The installed Chrome version on Android is 134.x.x.x or lower, or any version number less than 135.0.7049.52.
  4. Verify Chrome update availability
    On the Android device, open the Google Play Store app, search for Google Chrome, and check if an update is available or if the installed version matches the fixed release.
    Affected if Play Store shows an update is available, indicating the current version is older than the latest release.

A user is affected if Google Chrome is running on an Android device and the installed version is lower than 135.0.7049.52.

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 135.0.7049.52 or later
Fixed in 135.0.7049.52
Interim mitigation

Update Google Chrome on Android to version 135.0.7049.52 or later. Organizations should use MDM solutions to verify and enforce Chrome updates across managed devices.

Recommended fix High confidence

Chrome 135.0.7049.52 or later for Android

  1. Open the Google Play Store on your Android device
  2. Search for 'Google Chrome' or locate it in your installed apps
  3. Tap the 'Update' button if an update is available
  4. Wait for the update to download and install
  5. Alternatively, open Chrome, tap the three-dot menu, go to 'Help' > 'About Chrome', and tap 'Update' if available
  6. 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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