ChromeWeb browser · Google
CVE-2026-7355
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 Media 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: 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 confidenceUse-after-free vulnerability in Chrome's Media component prior to version 147.0.7727.138 allows a remote attacker to execute arbitrary code via a crafted HTML page. Although the sandbox restricts impact, successful exploitation can still lead to code execution within the sandboxed 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.
-
Confirm Google Chrome is installedCheck for Chrome executable: On Windows, look in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, run 'which google-chrome' or 'which chromium-browser'.Affected if Google Chrome is not installed on the system.
-
Determine installed Chrome versionOn Windows, right-click chrome.exe, select Properties, and view the File Version on the Details tab. On macOS, right-click Google Chrome.app, select Get Info, and check the Version field. Alternatively, open Chrome and navigate to chrome://settings/help to see the version displayed.Affected if Unable to determine the installed version.
-
Compare version against affected rangeCompare the installed version number to the affected range: any version less than 147.0.7727.138 is vulnerable. Chrome version numbers follow the format major.minor.build.patch (e.g., 147.0.7727.137 is vulnerable, 147.0.7727.138 is not).Affected if The installed version is less than 147.0.7727.138 (for example, 147.0.7727.137, 147.0.7727.100, 146.0.0.0, etc.).
The user is affected if Google Chrome is installed and the detected version is lower than 147.0.7727.138.
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 to patch the vulnerability. Deploy the update organization-wide using standard software deployment tools.
Chrome 147.0.7727.138 or later
- Open Google Chrome browser
- Click the three-dot menu icon in the top right corner
- Select 'Help' from the dropdown menu
- Click 'About Google Chrome'
- Chrome will automatically check for and install the latest version
- Restart the browser if prompted to complete the update
- Verify the version by returning to Help > About Google Chrome and confirm the version is 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
- Consultation3.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7355 — 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-7355 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