dbcve.org
ChromeWeb browser · Google

CVE-2026-7931

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
61/100
Remediation priority · Elevated
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
Insufficient validation of untrusted input in iOS in Google Chrome on iOS prior to 148.0.7778.96 allowed a remote attacker to perform UI spoofing 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 · high confidence

This is a UI spoofing vulnerability in Google Chrome on iOS caused by insufficient validation of untrusted input. A remote attacker can craft a malicious HTML page to manipulate the user interface, potentially tricking users into believing they are interacting with legitimate content. The vulnerability exists in Chrome versions prior to 148.0.7778.96 on iOS.

MitigationUpdate Google Chrome on iOS to version 148.0.7778.96 or later to address the insufficient input validation. Organizations should ensure mobile devices receive browser updates through their MDM or patch management processes.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L

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. Check if Google Chrome is installed on iOS
    Open the Settings app on the iOS device and scroll down to see if Google Chrome appears in the list of installed apps, or look for the Chrome icon on the home screen.
    Affected if Chrome iOS is not found in the device settings or not visible on the home screen, then this CVE does not apply.
  2. Identify the installed Chrome iOS version number
    Go to Settings > Chrome on the iOS device. The version number is displayed at the top of the Chrome settings page under the app name.
    Affected if This step is only applicable if Chrome iOS is installed.
  3. Compare the installed version to the affected range
    Check if the installed version number is less than 148.0.7778.96. For example, version 148.0.7778.95 or any earlier version is vulnerable.
    Affected if The installed version is lower than 148.0.7778.96, meaning the device is running a vulnerable version of Chrome on iOS.
  4. Confirm the attack surface exists
    Verify that the device has the capability to browse web pages using Chrome. This vulnerability is triggered when a user visits a malicious HTML page crafted by a remote attacker.
    Affected if Chrome iOS is used as the browser on the device; users who never launch Chrome or browse the web are not at direct risk from this specific flaw.

A user is affected if Google Chrome is installed on their iOS device and the installed version is below 148.0.7778.96.

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 on iOS to version 148.0.7778.96 or later to address the insufficient input validation. Organizations should ensure mobile devices receive browser updates through their MDM or patch management processes.

Recommended fix High confidence

Chrome for iOS 148.0.7778.96 or later

  1. Open the App Store on your iOS device
  2. Search for "Google Chrome" or locate it in your installed applications
  3. Tap the "Update" button to update Chrome for iOS to version 148.0.7778.96 or later
  4. Alternatively, enable automatic updates in iOS Settings > App Store > Automatic Downloads to ensure future security patches are applied automatically

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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