dbcve.org
ChromeWeb browser · Google

CVE-2024-11115

HIGH · 8.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 131.0.6778.69 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
Insufficient policy enforcement in Navigation in Google Chrome on iOS prior to 131.0.6778.69 allowed a remote attacker to perform privilege escalation via a series of UI gestures. (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 · moderate confidence

Insufficient policy enforcement in the Navigation component of Google Chrome on iOS prior to version 131.0.6778.69 allows a remote attacker to perform privilege escalation via a crafted series of UI gestures. The vulnerability stems from the browser failing to properly validate navigation policies, potentially allowing a malicious page to escape the sandbox or escalate privileges.

MitigationUpdate Google Chrome on iOS to version 131.0.6778.69 or later. Organizations should ensure mobile devices are running the latest Chrome version 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:< 131.0.6778.69

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. Check Chrome iOS version
    Open Chrome on iOS, tap the three-dot menu in the top-right corner, then tap Settings. Scroll down and tap 'Chrome' to view the version information displayed under the app name.
    Affected if The displayed version is lower than 131.0.6778.69 (for example, 131.0.6778.50 or earlier)

A user is affected if Google Chrome on iOS is installed and its version is below 131.0.6778.69.

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

Update Google Chrome on iOS to version 131.0.6778.69 or later. Organizations should ensure mobile devices are running the latest Chrome version through their MDM or patch management processes.

Recommended fix High confidence

Chrome on iOS version 131.0.6778.69 or later

  1. Open the App Store on your iOS device
  2. Search for "Google Chrome" or locate it in your installed apps
  3. Tap the Update button to download and install Chrome version 131.0.6778.69 or later
  4. After installation, verify the version by opening Chrome, tapping the three dots menu, selecting Settings, and checking the Chrome version

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-2024-11115 — 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-2024-11115 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