dbcve.org
ChromeWeb browser · Google

CVE-2026-10952

HIGH · 8.8 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 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
Use after free in Chrome for iOS in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (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 · high confidence

This is a use-after-free vulnerability in Google Chrome for iOS versions prior to 149.0.7827.53. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, causing heap corruption that could lead to arbitrary code execution.

MitigationUpdate Google Chrome for iOS to version 149.0.7827.53 or later. No server-side configuration changes are applicable as this is a client-side browser vulnerability.

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

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 for iOS installation
    On the iOS device, go to Settings > General > iPhone Storage (or Apps on iPad). Scroll down to locate Google Chrome in the list of installed applications.
    Affected if Google Chrome for iOS is not present on the device (not affected)
  2. Determine installed Chrome version
    Open Google Chrome on the iOS device, tap the three-dot menu, go to Settings, then tap Chrome to view the version information. Alternatively, navigate to chrome://version in the address bar.
    Affected if Version information cannot be retrieved or the browser is not Chrome for iOS
  3. Compare version against vulnerability threshold
    Compare the displayed version number to 149.0.7827.53. The version format typically appears as 149.x.x.x or similar.
    Affected if Installed version is less than 149.0.7827.53 (for example, 148.x.x.x or earlier)
  4. Assess active usage exposure
    Determine if the device actively uses Chrome for iOS for web browsing. Check if Chrome is set as the default browser or regularly used by device users.
    Affected if Chrome for iOS is actively used with a version below 149.0.7827.53

The environment is affected if any iOS device has Google Chrome for iOS installed with a version lower than 149.0.7827.53 and the browser is actively used for web browsing.

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

Update Google Chrome for iOS to version 149.0.7827.53 or later. No server-side configuration changes are applicable as this is a client-side browser vulnerability.

Recommended fix High confidence

149.0.7827.53 or later for Chrome on iOS

  1. 1. Open the App Store on your iOS device
  2. 2. Tap your profile icon in the top right corner
  3. 3. Scroll down to see available updates
  4. 4. Find Google Chrome in the list of apps with pending updates
  5. 5. Tap Update next to Google Chrome to install the latest version
  6. 6. Alternatively, search for Google Chrome in the App Store and tap Update if available
  7. 7. After updating, verify the version by opening Chrome, tapping the three dots menu, going to Settings, and checking About Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-10952 — 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-10952 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