dbcve.org
ChromeWeb browser · Google

CVE-2026-7913

HIGH · 7.8 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
81/100
Remediation priority · High
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
Insufficient policy enforcement in DevTools in Google Chrome on Android prior to 148.0.7778.96 allowed a local attacker to perform privilege escalation via a malicious file. (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

Insufficient policy enforcement in DevTools in Google Chrome on Android prior to version 148.0.7778.96 allows a local attacker to perform privilege escalation by tricking a user into opening a malicious file. The vulnerability stems from inadequate security policy controls within the DevTools component on the Android platform.

MitigationUpdate Google Chrome for Android to version 148.0.7778.96 or later to patch the insufficient policy enforcement vulnerability in DevTools.

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

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

CVSS:3.1/AV:L/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 Android platform
    Verify the device is running Android OS (not iOS, Windows, or other). Check Settings > About Phone > Android version.
    Affected if The device is not running Android - this CVE only affects Chrome on Android.
  2. Check Chrome version on Android
    Open Chrome > Settings > About Chrome (or navigate to chrome://version). Note the version number displayed.
    Affected if The installed Chrome version is lower than 148.0.7778.96, meaning the vulnerability is present in the installed version.
  3. Verify if DevTools debugging is accessible
    Check if USB debugging is enabled on the Android device (Settings > Developer Options > USB debugging) or if chrome://inspect shows any available targets. On Android Chrome, DevTools access typically requires enabling remote debugging.
    Affected if USB debugging is enabled AND Chrome version is below 148.0.7778.96 - the vulnerability can be exploited when an attacker connects via USB or accesses chrome://inspect.
  4. Check for malicious file handling context
    The vulnerability requires tricking a user into opening a malicious file. Review any recent APK or file downloads from untrusted sources that may have been opened in Chrome.
    Affected if A user has opened a malicious file on an affected Chrome version with DevTools debugging accessible, potentially enabling privilege escalation.

A user is affected if they are running Google Chrome on Android with version below 148.0.7778.96 and have DevTools debugging capabilities (USB debugging enabled or accessible chrome://inspect) exposed.

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

Update Google Chrome for Android to version 148.0.7778.96 or later to patch the insufficient policy enforcement vulnerability in DevTools.

Recommended fix High confidence

Chrome 148.0.7778.96 or later for Android

  1. Open Google Play Store on the Android device
  2. Search for "Google Chrome" or "Chrome"
  3. Tap "Update" if an update is available
  4. Alternatively, enable auto-updates: Go to Play Store > Menu > Settings > Auto-update apps > Select "Over any network" or "Over Wi-Fi only"
  5. Verify the updated version by opening Chrome > Settings > About Chrome - it should show 148.0.7778.96 or later
Caveat Chrome stable releases typically have minimal breaking changes; however, some legacy extensions or older Android versions (pre-Android 7.0) may have compatibility issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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