ChromeWeb browser · Google
CVE-2026-17804
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 151.0.7922.72 allowed a remote attacker who had compromised the renderer process 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 confidenceUse-after-free vulnerability in Chrome's Media component prior to version 151.0.7922.72 allows a remote attacker with prior renderer process compromise to potentially escape the sandbox via a crafted HTML page.
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
< 151.0.7922.72CVSS 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.
-
Find installed Chrome versionOpen Chrome and navigate to chrome://version, or click the three-dot menu > Help > About Google Chrome. Note the version number displayed.Affected if The version shown is earlier than 151.0.7922.72 (e.g., 151.0.7922.60, 150.x.x.x, etc.)
-
Verify exact version stringOn the chrome://version page, confirm the full version string including the build number (the number after the period). Chrome versions follow the format Major.Minor.Build.Revision.Affected if The full version number (e.g., 151.0.7922.60) is less than 151.0.7922.72 when compared numerically.
-
Confirm browser is actively usedDetermine whether Chrome is the primary or commonly used browser in the environment, as the vulnerability requires the browser to process specially crafted HTML content.Affected if Chrome is actively used and the installed version falls below 151.0.7922.72.
You are affected if the installed Google Chrome version is numerically lower than 151.0.7922.72, regardless of operating system, as the use-after-free in the Media component applies to all Chrome installations below that version.
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 · scoped151.0.7922.72
Update Google Chrome to version 151.0.7922.72 or later to patch the vulnerability.
Google Chrome 151.0.7922.72 or later
- Open Google Chrome
- Click the three-dot menu (top right)
- Select 'Help' > 'About Google Chrome'
- Chrome will check for updates and automatically download version 151.0.7922.72 or later
- Click 'Relaunch' to apply the update
- Verify the version by returning to Help > About Google Chrome and confirming version 151.0.7922.72 or newer is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-17804 — 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-17804 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