Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106373 Overview
CVE-2026-106373 is a use-after-free vulnerability in the Fonts component of Google Chrome on Windows. A remote attacker can execute arbitrary code inside the Chrome sandbox by serving a crafted HTML page to a targeted user. The flaw affects Chrome versions prior to 155.0.8059.39 on Windows. Google tracks the Chromium security severity as Medium, while the National Vulnerability Database rates it High based on CVSS impact metrics. Successful exploitation requires user interaction, typically visiting an attacker-controlled page. The weakness is classified under CWE-416: Use After Free.
Critical Impact
Arbitrary code execution within the Chrome renderer sandbox via a single crafted HTML page, enabling drive-by compromise of Windows browsers that have not updated to 155.0.8059.39.
Affected Products
- Google Chrome on Windows versions prior to 155.0.8059.39
- Microsoft Windows systems running vulnerable Chrome builds
- Chromium-based deployments inheriting the vulnerable Fonts code path
Discovery Timeline
- 2026-10-06 - CVE-2026-106373 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-106373
Vulnerability Analysis
The vulnerability resides in the Fonts component of Chrome's rendering pipeline on Windows. A use-after-free condition occurs when the browser retains a pointer to a font-related object after that object's memory has been released. An attacker who controls the lifecycle of this object through specific HTML, CSS, or font-loading constructs can trigger reuse of freed memory. The dangling pointer can then be reclaimed with attacker-controlled data, allowing arbitrary code execution inside the renderer sandbox. Although the renderer sandbox limits direct host impact, attackers routinely chain renderer flaws with sandbox-escape bugs to achieve full compromise.
Root Cause
The root cause is improper object lifetime management in the Fonts subsystem [CWE-416]. A reference to a freed font object persists past deallocation, violating ownership invariants and enabling type confusion or controlled memory reuse. See the Chromium Issue Tracker entry for upstream details.
Attack Vector
Exploitation is network-based and requires user interaction. The victim must load a crafted HTML page controlled by the attacker, delivered through phishing, malicious advertising, a compromised website, or a cross-origin frame. No authentication or prior access is required. Once the page renders, the font-parsing path triggers the use-after-free and executes attacker-supplied code within the Chrome renderer process.
No public proof-of-concept exploit is available for CVE-2026-106373. Technical specifics are described in prose per vendor coordinated disclosure practice; refer to the Chrome Stable Update Announcement and the Chromium Issue Tracker entry for additional context.
Detection Methods for CVE-2026-106373
Indicators of Compromise
- Chrome renderer processes (chrome.exe --type=renderer) crashing or spawning unexpected child processes after visiting external pages
- Outbound connections to unfamiliar domains originating from the Chrome process shortly after page load
- HTML content containing unusual @font-face declarations referencing malformed or oversized font resources
- Browser telemetry showing Chrome versions below 155.0.8059.39 on Windows endpoints
Detection Strategies
- Inventory installed Chrome versions across Windows fleets and flag any build earlier than 155.0.8059.39
- Monitor process trees for renderer processes launching shells, rundll32.exe, powershell.exe, or other living-off-the-land binaries
- Inspect web proxy logs for pages serving crafted font files combined with scripted DOM manipulation of font elements
Monitoring Recommendations
- Enable endpoint detection and response telemetry for Chrome child-process creation and memory anomalies
- Correlate browser crash reports from Windows Error Reporting with suspicious outbound network activity
- Alert on Chrome processes writing executables or scripts to disk under user profile directories
How to Mitigate CVE-2026-106373
Immediate Actions Required
- Update Google Chrome on Windows to version 155.0.8059.39 or later immediately
- Restart all Chrome instances after the update to ensure the patched binary is loaded
- Verify managed Chrome deployments through enterprise policy to confirm the fixed version is enforced
- Prioritize patching for high-risk users such as executives, developers, and administrators
Patch Information
Google fixed CVE-2026-106373 in Chrome Stable channel version 155.0.8059.39 for Windows. Patch details are published in the Chrome Stable Update Announcement. Chromium-based browsers that embed the affected Fonts code should rebase on the corresponding upstream fix.
Workarounds
- No vendor-supplied workaround exists; applying the patch is the only complete mitigation
- Restrict browsing to trusted sites via web filtering until all endpoints are updated
- Deploy enterprise policy to force Chrome auto-update and disable version pinning that holds back the fix
- Consider temporarily blocking untrusted external advertising networks that commonly deliver drive-by exploit content
# Enforce Chrome auto-update via Windows Group Policy registry keys
reg add "HKLM\SOFTWARE\Policies\Google\Update" /v AutoUpdateCheckPeriodMinutes /t REG_DWORD /d 60 /f
reg add "HKLM\SOFTWARE\Policies\Google\Update" /v UpdateDefault /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Google\Update" /v "Update{8A69D345-D564-463C-AFF1-A69D9E530F96}" /t REG_DWORD /d 1 /f
# Verify installed Chrome version
(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

