ChromeWeb browser · Google
CVE-2026-11165
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 · uneditedUse after free in WebMIDI in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape 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 confidenceA use-after-free vulnerability in the WebMIDI API implementation in Google Chrome on iOS allows a remote attacker to potentially escape the browser's sandbox through a specially crafted HTML page. This memory corruption issue exists in versions prior to 149.0.7827.53 and can be exploited without user interaction beyond visiting a malicious webpage.
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
< 149.0.7827.53CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Google Chrome on iOSCheck if Google Chrome browser app is installed on the iOS device by looking in the app library or home screenAffected if Chrome iOS app is present on the device
-
Determine Chrome iOS versionOpen Chrome, tap the three-dot menu, go to Settings, then tap Chrome to view the version number, or navigate to chrome://version in the address barAffected if The displayed version is lower than 149.0.7827.53 (e.g., 148.x.x.x or earlier)
-
Verify WebMIDI API accessibilitySince WebMIDI is a web API available to JavaScript in Chrome, any webpage can attempt to access navigator.requestMIDIAccess(). Check if Chrome has not restricted this API via enterprise policiesAffected if WebMIDI API calls execute without errors (API is enabled) and Chrome version is below 149.0.7827.53
A user is affected if Google Chrome on iOS is installed with a version lower than 149.0.7827.53 and the WebMIDI API is accessible, allowing a malicious webpage to trigger the use-after-free vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped149.0.7827.53
Update Google Chrome for iOS to version 149.0.7827.53 or later to patch the vulnerability. Organizations should ensure auto-updates are enabled or deploy the updated browser version via MDM.
Chrome for iOS 149.0.7827.53 or later
- Open the App Store app on your iOS device
- Tap your profile picture in the upper right corner
- Scroll down to view available updates
- Locate Google Chrome in the list of pending updates
- Tap Update next to Google Chrome to install version 149.0.7827.53 or later
- Alternatively, search for Google Chrome in the App Store and tap Update if an update is available
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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