CVE-2026-106377 in Chromeinfo

Summary

by MITRE • 10/07/2026

Race condition in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 10/07/2026

The vulnerability identified as CVE-2024-6715 represents a critical race condition within the font handling subsystem of Google Chrome, specifically affecting versions prior to 155.0.8059.39. This flaw resides in the complex logic governing how fonts are loaded, cached, and rendered on web pages. Race conditions typically arise when software performs two or more operations out of order or without proper synchronization mechanisms such as locks or mutexes. In this specific context, the vulnerability allows for a scenario where an attacker can manipulate the timing of font resource requests relative to internal state updates within the browser engine. This temporal discrepancy creates a window of opportunity where the application may process data in an inconsistent state, leading to memory corruption or unauthorized access patterns that bypass intended security controls.

The operational impact of this vulnerability is severe due to its potential for privilege escalation from a sandboxed environment to arbitrary code execution on the host system. Google Chrome employs a multi-process architecture with strict sandboxes designed to isolate web content and prevent malicious scripts from accessing sensitive user data or executing commands outside their restricted context. The renderer process, which handles the parsing and rendering of HTML, CSS, and JavaScript for each tab, is heavily sandboxed to limit its capabilities. However, by exploiting this race condition in the font subsystem, a remote attacker who has already compromised the renderer process through another vector can leverage this flaw to escape the sandbox boundary. This means that code executed within the browser context gains elevated privileges equivalent to those of the user running the browser, effectively neutralizing one of the primary defense-in-depth layers provided by modern web browsers.

From an industry standards perspective, this vulnerability aligns with CWE-362, which defines concurrent execution race conditions where shared resources are accessed without proper synchronization. The exploitation technique also maps closely to MITRE ATT&CK techniques related to process injection and sandbox escape, specifically T1055 Process Injection or T1047 Windows Executable File, depending on the underlying operating system's implementation details within Chromium. The ability to execute arbitrary code outside the sandbox is a classic indicator of an out-of-bounds write or use-after-free scenario facilitated by timing attacks against internal data structures. Such vulnerabilities are particularly dangerous because they often require sophisticated exploitation chains and may not have immediate public proof-of-concept code, allowing attackers to maintain persistent access before patches are widely deployed.

Mitigation for this vulnerability requires the immediate update of Google Chrome to version 155.0.8059.39 or later, where the race condition in the font handling logic has been resolved through improved synchronization mechanisms and stricter validation checks during resource loading. For organizations managing large fleets of devices, deploying automated patch management solutions is essential to ensure timely remediation across all endpoints. Additionally, security teams should monitor for indicators of compromise associated with renderer process exploitation, such as unusual memory allocation patterns or attempts to load unsigned binaries from temporary directories. While technical mitigations like sandboxing remain effective against many threats, they are not impervious to sophisticated race condition exploits; therefore, keeping software up-to-date remains the most reliable defense strategy against this class of vulnerabilities.

Responsible

Chrome

Reservation

10/06/2026

Disclosure

10/07/2026

Moderation

accepted

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!