dbcve.org
ChromeWeb browser · Google

CVE-2026-7957

HIGH · 8.8 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 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
Out of bounds write in Media in Google Chrome on Mac, iOS prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox 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

Out-of-bounds write vulnerability in the Media component of Google Chrome on Mac and iOS allows a remote attacker with a compromised renderer process to execute arbitrary code within the sandbox via a crafted HTML page.

MitigationUpdate Google Chrome for Mac and iOS to version 148.0.7778.96 or later. Ensure automatic updates are enabled and the sandbox is functioning as designed.

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
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 installation
    On Mac: Open Finder, go to /Applications folder, confirm Google Chrome.app exists. On iOS: Check the home screen for the Chrome app icon.
    Affected if Chrome is not installed on the device
  2. Determine installed Chrome version
    On Mac: Launch Chrome, click the Chrome menu in the menu bar, select About Google Chrome. On iOS: Open the App Store app, tap your profile icon, scroll to Chrome in the app list to view the available update version.
    Affected if Unable to retrieve the installed version number
  3. Compare version against affected threshold
    Take the installed version number (for example, 148.0.7778.95) and compare it numerically to 148.0.7778.96. Any version with a lower major, minor, build, or patch number is in the affected range.
    Affected if Installed version is 148.0.7778.95 or earlier (any version below 148.0.7778.96)
  4. Confirm platform is Mac or iOS
    This vulnerability specifically targets Chrome on Mac and iOS. On Mac: System Settings > General > About displays the macOS version. On iOS: Settings > General > About > Software Version displays the iOS version.
    Affected if Running Chrome on Windows, Linux, Android, or other platforms not listed in affected products

The environment is affected if Google Chrome is installed on Mac or iOS with a version number lower than 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 for Mac and iOS to version 148.0.7778.96 or later. Ensure automatic updates are enabled and the sandbox is functioning as designed.

Recommended fix High confidence

148.0.7778.96

  1. Open Google Chrome browser
  2. Navigate to Settings > Help > About Google Chrome (or visit chrome://settings/help)
  3. Chrome will automatically check for updates
  4. If version 148.0.7778.96 or later is available, click 'Update Google Chrome' or allow it to update automatically
  5. Restart the browser after the update completes
  6. Verify the version by returning to About Google Chrome and confirming the installed version is 148.0.7778.96 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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