ChromeWeb browser · Google
CVE-2026-7336
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 WebRTC in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to execute arbitrary code inside a sandbox 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 · moderate confidenceA use-after-free vulnerability exists in the WebRTC component of Google Chrome versions prior to 147.0.7727.138. This memory corruption flaw allows a remote attacker who tricks a user into visiting a crafted HTML page to execute arbitrary code within the browser's sandbox context.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Chrome executable: On Windows, look for chrome.exe in Program Files or Program Files (x86). On macOS, check /Applications/Google Chrome.app. On Linux, check for google-chrome in common binary paths.Affected if Chrome browser is present on the system
-
Retrieve installed Chrome versionNavigate to chrome://settings/help in the Chrome address bar, or run 'google-chrome --version' from command line on Linux/macOS, or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome on Windows.Affected if Unable to determine version (Chrome may be installed but not accessible)
-
Compare version against CVE thresholdParse the version number found and compare it numerically to 147.0.7727.138. The affected range is any version less than 147.0.7727.138.Affected if Installed version is lower than 147.0.7727.138 (for example, 147.0.7727.100 or 146.0.6498.115)
User is affected if Google Chrome is installed with a version lower than 147.0.7727.138 and the user can open arbitrary web pages in the browser.
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 deploy the browser update through their patch management infrastructure and verify the update was applied successfully.
Chrome version 147.0.7727.138 or later
- Open Google Chrome and navigate to Help > About Google Chrome
- Verify the current version is below 147.0.7727.138
- Click 'Update Google Chrome' if an update is available
- Restart the browser after the update completes
- Confirm the version shows 147.0.7727.138 or later after restart
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 / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7336 — 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-7336 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