ChromeWeb browser · Google
CVE-2026-10972
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.53 allowed a remote attacker to potentially perform a sandbox escape 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 the Ozone windowing system in Google Chrome on Linux versions prior to 149.0.7827.53 allows a remote attacker to escape the Chromium sandbox and potentially execute arbitrary code by tricking users into visiting a crafted HTML page.
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.53CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome is installed on LinuxRun command: which google-chrome or ls /usr/bin/google-chromeAffected if Chrome is not found - not affected; if found, proceed to version check
-
Check installed Chrome versionRun command: google-chrome --version or google-chrome-stable --versionAffected if Output shows version number less than 149.0.7827.53 - vulnerable
-
Confirm Linux platformRun command: uname -s to verify Linux kernel; Chrome on other platforms (Windows, macOS) use different platform layers and are not affected by this Ozone-specific flawAffected if Not Linux - not affected by this specific Ozone vulnerability
-
Verify Chrome component affectedThis vulnerability is in Ozone, Chrome's platform abstraction layer specific to Linux; it requires the browser to be running on Linux with Ozone enabled, which is the default for Chrome on LinuxAffected if Running Chrome on Linux below version 149.0.7827.53 - affected and vulnerable
User is affected if running Google Chrome on Linux with version below 149.0.7827.53, since the use-after-free in Ozone only applies to Chrome's Linux platform layer.
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.53
Update Google Chrome to version 149.0.7827.53 or later on all Linux systems; in enterprise environments, deploy the update organization-wide via patch management tooling.
Chrome 149.0.7827.53 or later (Linux)
- 1. Open Google Chrome on the affected Linux system
- 2. Navigate to Chrome Settings (three-dot menu)
- 3. Click 'About Chrome' in the left sidebar
- 4. Chrome will automatically check for updates and download version 149.0.7827.53 or later
- 5. Click 'Restart' to apply the update
- 6. Alternatively, download the latest stable Chrome from https://www.google.com/chrome/ and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10972 — 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-10972 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