ChromeWeb browser · Google
CVE-2026-7363
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 Canvas in Google Chrome on Linux, ChromeOS 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: Critical)
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 in the Canvas rendering component of Google Chrome on Linux and ChromeOS allows a remote attacker to execute arbitrary code inside the sandbox via a maliciously crafted HTML page. The vulnerability exists in versions prior to 147.0.7727.138.
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.
-
Identify the operating systemRun 'uname -a' or check system settings to confirm the platform. On Linux, run 'cat /etc/os-release' for distribution details.Affected if The platform is NOT Linux or ChromeOS (the vulnerability only affects these platforms)
-
Verify Google Chrome is installedRun 'google-chrome --version' or 'chrome --version' in the terminal. On ChromeOS, check chrome://version in the browser.Affected if Google Chrome is not installed on the system
-
Check the installed Chrome versionExecute 'google-chrome --version' and note the version number returned. Compare the full version string against 147.0.7727.138.Affected if The installed version is lower than 147.0.7727.138 (e.g., 147.0.7727.100 or earlier)
-
Confirm the vulnerability scopeNote that the flaw is in the Canvas rendering component and requires user interaction (visiting a crafted HTML page). The attack vector is remote but limited by Chrome's sandbox.Affected if The user runs an affected Chrome version on Linux or ChromeOS and can be persuaded to visit untrusted web pages
A user is affected if they are running Google Chrome version lower than 147.0.7727.138 on Linux or ChromeOS platforms, as the use-after-free vulnerability in the Canvas rendering component can be exploited via malicious web pages.
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 on all affected Linux and ChromeOS endpoints.
147.0.7727.138 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- The browser will automatically check for updates
- If version 147.0.7727.138 or later is available, click 'Update Google Chrome'
- Restart the browser to complete the installation
- Alternatively, download the latest stable version directly from the official Google Chrome website
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 / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7363 — 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-7363 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