CVE-2026-10899: Use after free in Ozone
Chromium: CVE-2026-10899 Use after free in Ozone
Other sources
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
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)
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Chromium (Google Chrome/Edge Chromium-based)to a version that resolves this vulnerability.Fixed in 149.0.7827.53
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-8555
- CVE-2026-7906
- CVE-2026-7926
- CVE-2026-7360
- CVE-2026-7355
- CVE-2026-7335
- CVE-2026-11644
- CVE-2026-7910
- CVE-2026-6314
- CVE-2026-6316
- CVE-2026-6312
- CVE-2026-7349
- CVE-2026-6362
- CVE-2026-7908
- CVE-2026-7333
- CVE-2026-10015
- CVE-2026-6317
- CVE-2026-11628
- CVE-2026-3924
- CVE-2026-7341
- CVE-2026-7345
- CVE-2026-7898
- CVE-2026-11643
- CVE-2026-9906
- CVE-2026-10972
- CVE-2026-11642
- CVE-2026-10884
- CVE-2026-11638
- CVE-2026-11640
- CVE-2026-10893
- CVE-2026-6313
- CVE-2026-11629
- CVE-2026-11632
- CVE-2026-10886
- CVE-2026-10902
- CVE-2026-10891
- CVE-2026-10895
- CVE-2026-10898
- CVE-2026-99220
Frequently Asked Questions
What is the severity of CVE-2026-10899?
The severity of CVE-2026-10899 is high with a CVSS score of 7.5.
How do I fix CVE-2026-10899?
To fix CVE-2026-10899, update Google Chrome to version 149.0.7827.53 or later.
What systems are affected by CVE-2026-10899?
CVE-2026-10899 affects Google Chrome on Linux prior to version 149.0.7827.53 and Microsoft Edge (Chromium-based) that relies on Chromium.
What type of vulnerability is CVE-2026-10899?
CVE-2026-10899 is classified as a Use After Free vulnerability.
Is CVE-2026-10899 being actively exploited?
As of the latest updates, there are indications that CVE-2026-10899 may be actively exploited in the wild.