ChromeWeb browser · Google
CVE-2026-9111
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 WebRTC in Google Chrome on Linux prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code 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 · moderate confidenceThis is a Use After Free (UAF) vulnerability in the WebRTC component of Google Chrome on Linux. A remote attacker can exploit this by tricking users into visiting a specially crafted HTML page, which allows arbitrary code execution. The vulnerability affects versions prior to 148.0.7778.179.
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
< 148.0.7778.179CVSS 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 Google Chrome version on LinuxOpen terminal and run: google-chrome --version OR chromium --versionAffected if Version number is lower than 148.0.7778.179
-
Verify Chrome/Chromium package detailsCheck package manager: dpkg -l | grep -i chromium OR rpm -q chromium (depending on package system)Affected if Installed package version is shown as earlier than 148.0.7778.179
-
Confirm WebRTC module presenceOpen chrome://version in the browser and look for WebRTC components, or check /usr/lib/chromium/ or /opt/google/chrome/ directories for WebRTC related librariesAffected if WebRTC component files exist on the system
-
Check if Chrome is actively used on LinuxVerify Chrome/Chromium browser is installed and functional: which google-chrome OR which chromiumAffected if Google Chrome or Chromium browser is installed and running on Linux with version below 148.0.7778.179
A Linux user is affected if they run any version of Google Chrome or Chromium browser on Linux that is older than version 148.0.7778.179, with the WebRTC component present and accessible.
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 · scoped148.0.7778.179
Update Google Chrome to version 148.0.7778.179 or later on all affected Linux systems. Organizations should deploy this update via their standard endpoint management tools.
148.0.7778.179 or later (stable release)
- Open a terminal on the Linux system
- Update the package repository by running: sudo apt-get update (or the equivalent for your package manager)
- Upgrade Chrome by running: sudo apt-get upgrade google-chrome-stable (or sudo apt-get upgrade chrome-browser)
- Wait for the upgrade to complete, then restart the Google Chrome browser
- Verify the installed version by navigating to chrome://settings/help - it should show version 148.0.7778.179 or later
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-9111 — 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-9111 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