dbcve.org
ChromeWeb browser · Google

CVE-2025-3067

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 Custom Tabs in Google Chrome on Android prior to 135.0.7049.52 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform privilege escalation via a crafted app. (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 · high confidence

A vulnerability in Google Chrome's Custom Tabs feature on Android allowed a crafted malicious app to perform privilege escalation by tricking users into performing specific UI gestures. The inappropriate implementation failed to properly validate or restrict these gestures, enabling unauthorized actions.

MitigationUpdate Google Chrome on Android to version 135.0.7049.52 or later. For enterprise environments, deploy the update via mobile device management (MDM) tools to ensure all managed devices receive 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:< 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. Verify Google Chrome is installed on the Android device
    Navigate to Settings > Apps on the Android device and look for Google Chrome in the app list, or check the app drawer for the Chrome icon
    Affected if Chrome is not installed on the device (not affected)
  2. Determine the installed Chrome version
    Open Google Chrome, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed at the top of the screen
    Affected if Version number cannot be retrieved or Chrome is not present
  3. Compare the installed version against the affected range
    Compare the version shown in About Chrome to the affected version 135.0.7049.52. Chrome versions follow format like 135.0.7049.x
    Affected if Installed version is less than 135.0.7049.52 (for example, 135.0.7049.42 or any 134.x.x version)
  4. Check for third-party apps with Custom Tabs permission
    On Android, go to Settings > Apps > chrome and review which apps are listed as having permission to open content in Chrome (this indicates Custom Tab usage)
    Affected if Many untrusted third-party apps are present with Chrome integration permissions, combined with a vulnerable Chrome version

The device is affected if Google Chrome for Android is installed with a version lower than 135.0.7049.52, regardless of Custom Tabs usage since the feature is built into Chrome.

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. For enterprise environments, deploy the update via mobile device management (MDM) tools to ensure all managed devices receive the patch.

Recommended fix High confidence

Chrome 135.0.7049.52 for Android

  1. Open the Google Play Store app on the Android device
  2. Search for 'Google Chrome' in the search bar
  3. Tap on the Chrome app from the search results
  4. If an update is available, tap the 'Update' button
  5. Wait for the update to download and install completely
  6. Launch Chrome after the update completes to ensure the new version (135.0.7049.52 or later) is running
Caveat Minimal - security update with no expected breaking changes for standard usage

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-3067 — 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-3067 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