ChromeWeb browser · Google
CVE-2026-7350
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 prior to 147.0.7727.138 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidenceA use-after-free vulnerability exists in WebMIDI in Google Chrome before version 147.0.7727.138. An attacker who has already compromised the renderer process can exploit this memory corruption flaw via a crafted HTML page to potentially escape the Chrome sandbox and execute code outside the sandboxed environment.
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
< 147.0.7727.138CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Determine installed Chrome versionOpen chrome://version in the Chrome address bar and note the version number shown under 'Google Chrome'Affected if Version number is less than 147.0.7727.138
-
Verify Chrome update statusNavigate to chrome://settings/help and check if the browser reports it is up to date or shows an available updateAffected if Browser reports update available or version is outdated
-
Check if WebMIDI API is accessibleOpen Developer Tools (F12), go to Console, and run: 'if (navigator.requestMIDIAccess) { console.log("WebMIDI available"); } else { console.log("WebMIDI not available"); }'Affected if WebMIDI API returns as available (not blocked or disabled)
-
Confirm WebMIDI policy settingNavigate to chrome://settings/content/midi or check Group Policy settings for WebMIDI API permissionAffected if WebMIDI is allowed or not explicitly blocked by policy
User is affected if Chrome version is below 147.0.7727.138 AND WebMIDI API is accessible in the browser environment.
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 · scoped147.0.7727.138
Update Google Chrome to version 147.0.7727.138 or later. Organizations should also ensure their endpoint protection and browser update management systems are current, as this vulnerability requires renderer process compromise as a prerequisite.
Chrome 147.0.7727.138 or later (stable channel)
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 147.0.7727.138, click 'Update Google Chrome' to download and install the latest version
- Alternatively, download the latest stable Chrome from the official website (google.com/chrome)
- After the update installs, restart Chrome to complete the remediation
- Verify the version now shows 147.0.7727.138 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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7350 — 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-7350 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