ChromeWeb browser · Google
CVE-2026-6318
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 Codecs in Google Chrome prior to 147.0.7727.101 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 confidenceA use-after-free vulnerability exists in the Codecs component of Google Chrome versions prior to 147.0.7727.101. The flaw allows a remote attacker to execute arbitrary code via a specially crafted HTML page, exploiting the freed memory after the pointer is released.
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.101CVSS 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.
-
Check installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' (Linux) or 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' (Windows) in command promptAffected if Version number is lower than 147.0.7727.101
-
Verify Chrome is present on endpointCheck for Chrome installation directory: Linux typically at /usr/bin/google-chrome or ~/.local/bin/google-chrome; Windows typically at C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Users\<user>\AppData\Local\Google\Chrome\Application\chrome.exeAffected if Chrome executable exists and version cannot be determined or is below 147.0.7727.101
-
Identify users processing untrusted HTMLReview endpoints where users browse the web or open HTML files from untrusted sources, particularly where media (audio/video) content is renderedAffected if Chrome versions below 147.0.7727.101 are in use and the browser processes HTML content from external or untrusted sources
The environment is affected if any installed Google Chrome version is below 147.0.7727.101 and the browser processes untrusted HTML content.
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.101
Update Google Chrome to version 147.0.7727.101 or later to patch the vulnerability. Apply the update through standard patch management processes across all affected systems.
Chrome 147.0.7727.101 or later
- Open Google Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is earlier than 147.0.7727.101, click 'Update Google Chrome' to download and install the latest version
- Restart Chrome after the update completes to apply the fix
- Verify the version now shows 147.0.7727.101 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6318 — 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-6318 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