ChromeWeb browser · Google
CVE-2026-11681
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 Ozone in Google Chrome on Linux prior to 149.0.7827.103 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 Ozone (Chrome's platform abstraction layer) on Linux that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page in Google Chrome versions prior to 149.0.7827.103.
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
< 149.0.7827.102CVSS 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.
-
Confirm Linux operating systemRun 'uname -a' or check /etc/os-release to verify the host is running Linux. This vulnerability only affects Chrome on Linux, not other platforms.Affected if The system is NOT Linux - if running Windows, macOS, or other OS, this CVE does not apply.
-
Verify Chrome is installedRun 'google-chrome --version' or 'chromium --version' in terminal. Alternatively, check the installed package via 'dpkg -l | grep -i chrome' or 'rpm -qa | grep -i chrome' depending on package manager.Affected if Chrome or Chromium is not installed - the vulnerability cannot affect a system without the browser.
-
Compare installed version to affected rangeThe installed version must be below 149.0.7827.102. Check the exact version number from step 2 and compare. Versions 149.0.7827.102 and below are affected; 149.0.7827.103 and above are fixed.Affected if Installed version is less than 149.0.7827.102 (e.g., 149.0.7827.101, 148.0.4095.111, etc.)
-
Confirm Ozone display component is in useOn Linux, Chrome uses the Ozone display backend by default for graphics rendering. No additional configuration check is typically needed as this is the standard display component for Chrome on Linux.Affected if This is a default component for Chrome on Linux and is typically always enabled. The check is primarily for version determination in step 3.
A system is affected if it runs Google Chrome or Chromium on Linux with a version lower than 149.0.7827.102.
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 · scoped149.0.7827.102
Upgrade Google Chrome for Linux to version 149.0.7827.103 or later to remediate the use-after-free vulnerability.
Chrome 149.0.7827.103 or later for Linux
- Open Google Chrome on the Linux system
- Click the three-dot menu in the top-right corner
- Navigate to Help > About Google Chrome
- Chrome will check for updates and automatically download the latest version
- Restart Chrome after the update completes to apply the fix
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11681 — 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-11681 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