dbcve.org
ChromeWeb browser · Google

CVE-2026-10899

HIGH · 7.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Use after free in Ozone in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption 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 confidence

Use-after-free vulnerability in the Ozone windowing system component of Google Chrome on Linux allows a remote attacker who tricks a user into performing specific UI gestures to potentially exploit heap corruption via a crafted HTML page, affecting versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later on all affected Linux systems to patch the use-after-free vulnerability.

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
Affected:< 149.0.7827.53

CVSS 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Linux environment
    Verify the operating system is Linux (the vulnerability exists in Ozone, Chrome's platform abstraction layer specifically on Linux)
    Affected if Running on Linux - this vulnerability only affects Chrome on Linux systems
  2. Check if Google Chrome is installed
    Run command: which google-chrome or which chromium-browser
    Affected if Google Chrome or Chromium is installed on the system
  3. Determine installed Chrome version
    Run command: google-chrome --version or chromium-browser --version
    Affected if Version is returned by the command and is less than 149.0.7827.53
  4. Compare version against affected range
    Compare the installed version number to the affected range: versions prior to 149.0.7827.53 are vulnerable
    Affected if Installed version is lower than 149.0.7827.53 (for example: 148.x.x.x or earlier)
  5. Verify Chrome profile and user interaction context
    Note that exploitation requires a user to be tricked into interacting with crafted HTML content - check if browser is used to navigate untrusted web pages
    Affected if Users may be persuaded to interact with malicious HTML pages rendered in the browser

A user is affected if running Google Chrome or Chromium on Linux with a version lower than 149.0.7827.53 and the browser is used to view potentially untrusted web content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome to version 149.0.7827.53 or later on all affected Linux systems to patch the use-after-free vulnerability.

Recommended fix High confidence

149.0.7827.53 or later (Chrome Stable channel)

  1. Open a terminal and update your system package repository by running: sudo apt update (or your distribution's equivalent package update command)
  2. Upgrade Google Chrome by running: sudo apt upgrade google-chrome-stable (or sudo dnf update google-chrome-stable on Fedora/RHEL-based systems)
  3. Alternatively, download the latest stable Chrome from https://www.google.com/chrome/ and reinstall
  4. Restart Chrome to ensure the updated version (149.0.7827.53 or later) is running
  5. Verify the installed version by navigating to chrome://settings/help or running: google-chrome --version

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10899 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10899 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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