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-110147 Overview
CVE-2026-110147 is a use-after-free vulnerability in the PDF component of Google Chrome prior to version 155.0.8059.79. A remote attacker can exploit the flaw by serving a crafted HTML page that triggers unsafe reuse of freed memory within the PDF rendering pipeline. Successful exploitation allows arbitrary code execution inside the Chrome sandbox. The issue is tracked under CWE-416: Use After Free and was addressed in the Chrome Stable channel update for desktop. Google rates the Chromium security severity as High.
Critical Impact
Remote attackers can execute arbitrary code inside the Chrome sandbox by luring a user to a crafted HTML page that embeds a malicious PDF.
Affected Products
- Google Chrome for Desktop versions prior to 155.0.8059.79
- Chromium-based browsers that embed the vulnerable PDF component
- Any downstream distribution shipping Chrome releases older than 155.0.8059.79
Discovery Timeline
- 2026-10-13 - CVE-2026-110147 published to the National Vulnerability Database
- 2026-10-14 - Last updated in the NVD database
Technical Details for CVE-2026-110147
Vulnerability Analysis
The flaw resides in Chrome's PDF subsystem, which renders PDF content embedded in or loaded from HTML pages. A use-after-free condition occurs when the PDF component continues to reference memory that has already been released. An attacker who controls the page content can shape allocator state so that the freed object is replaced with attacker-controlled data. Dereferencing the stale pointer then yields control over execution within the renderer process. Because the PDF code runs inside the sandboxed renderer, exploitation requires user interaction with a crafted HTML page but does not require authentication.
Root Cause
Use-after-free bugs [CWE-416] arise when object lifetime management diverges from how the object is actually used. In this case, a PDF object is freed while another code path still holds a reference to it. Subsequent operations on that reference read or write memory that may have been reallocated for an unrelated purpose. The vulnerability details reside in the restricted Chromium Issue Tracker Entry and are not public.
Attack Vector
Exploitation is network-based and requires the victim to load a crafted HTML page in a vulnerable Chrome build. The page delivers PDF content that drives the vulnerable code path to free an object and then reuse it. Attackers can combine typical browser exploitation techniques, such as heap grooming and JavaScript-driven allocator manipulation, to reclaim the freed slot with controlled data. The result is arbitrary code execution within the renderer sandbox. A separate sandbox escape would be required to achieve code execution on the host operating system.
No verified exploit code is available for CVE-2026-110147.
See the Chromium Issue Tracker Entry for restricted technical details.
Detection Methods for CVE-2026-110147
Indicators of Compromise
- Renderer process crashes referencing the PDF plugin or pdfium modules on hosts running Chrome versions earlier than 155.0.8059.79.
- Browser telemetry showing navigation to untrusted sites that serve embedded or inline PDF content immediately preceding a renderer crash.
- Unexpected child process creation or outbound network connections originating from the Chrome renderer process after loading PDF content.
Detection Strategies
- Inventory Chrome installations and flag any instance below version 155.0.8059.79 as exposed.
- Correlate endpoint telemetry for Chrome renderer crashes with web proxy logs showing recent PDF downloads or application/pdf content types.
- Hunt for post-exploitation behavior such as script interpreters, LOLBins, or credential access tools spawned by chrome.exe or its helper processes.
Monitoring Recommendations
- Enable Chrome enterprise reporting to centralize crash and version data for analysis.
- Monitor proxy and DNS logs for repeated visits to low-reputation domains serving PDF payloads.
- Alert on anomalous process lineage where Chrome renderer processes spawn non-browser child processes.
How to Mitigate CVE-2026-110147
Immediate Actions Required
- Update Google Chrome to version 155.0.8059.79 or later on all Windows, macOS, and Linux endpoints.
- Restart Chrome after the update completes to ensure the patched binaries are loaded.
- Verify that Chromium-based browsers and embedded Chromium frameworks in your environment have pulled the fixed PDF component.
Patch Information
Google addressed the vulnerability in the Chrome Stable channel release documented in the Google Chrome Desktop Update. Administrators should confirm deployment of Chrome 155.0.8059.79 or newer. Technical details about the specific fix are restricted in the Chromium Issue Tracker Entry until a majority of users have updated.
Workarounds
- Enforce automatic Chrome updates through enterprise policy so endpoints receive the fixed build without user action.
- Restrict access to untrusted sites that serve PDF content using web filtering until all endpoints are patched.
- Consider disabling the built-in Chrome PDF viewer via the AlwaysOpenPdfExternally enterprise policy as a temporary measure for high-risk users.
# Example Chrome enterprise policy to force PDFs to download instead of render in-browser
# Linux: /etc/opt/chrome/policies/managed/pdf.json
{
"AlwaysOpenPdfExternally": true
}
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

