ChromeWeb browser · Google
CVE-2026-14121
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 Chromoting in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Low)
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 confidenceUse after free vulnerability in Chrome's Chromoting (remote desktop) component on Linux systems allows remote attackers to execute arbitrary code via malicious network traffic. The flaw exists in versions prior to 150.0.7871.47.
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
< 150.0.7871.47CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 the operating system is LinuxRun 'uname -a' or check '/etc/os-release' to confirm the system is running Linux. This vulnerability only affects Chrome on Linux systems.Affected if The system is running Linux - other operating systems are not affected by this CVE.
-
Check if Google Chrome is installedRun 'google-chrome --version' or 'google-chrome-stable --version' in the terminal. If these commands fail, Chrome may not be installed.Affected if Google Chrome is not installed - the vulnerability does not apply.
-
Obtain the installed Google Chrome version numberExecute 'google-chrome --version' or 'google-chrome-stable --version' and note the full version string (e.g., 150.0.7871.47).Affected if Unable to determine the installed version - cannot assess vulnerability status.
-
Compare installed version against the affected rangeCompare the installed version number to 150.0.7871.47. Versions below 150.0.7871.47 are affected; versions 150.0.7871.47 and above are patched.Affected if The installed version is less than 150.0.7871.47 - the system is vulnerable to the use-after-free flaw in the Chromoting component.
A user is affected if they are running Google Chrome on Linux with a version number lower than 150.0.7871.47.
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 · scoped150.0.7871.47
Update Google Chrome for Linux to version 150.0.7871.47 or later to patch the use-after-free vulnerability.
150.0.7871.47
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for and download the latest update
- If version 150.0.7871.47 or later is available, click 'Update Google Chrome'
- Restart the browser to complete the update
- Verify the update by returning to Help > About Google Chrome and confirming the version is 150.0.7871.47 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-14121 — 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-14121 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