CVE-2026-110147 Google CVE debrief

Who should care

Chrome browser users, particularly those with high-risk exposure or requiring strict security controls, should assess their exposure and update to the latest version. Chrome users with high-risk exposure, such as those in critical infrastructure or high-risk industries, should prioritize updating to version 155.0.8059.79 or later. Additionally, Chrome browser administrators should review and monitor Chrome browser logs for suspicious activity and implement

Why it matters

CVE-2026-110147 is a high-severity use-after-free vulnerability in Google Chrome's PDF component that allows remote code execution inside the sandbox. Chrome users, especially those with high-risk exposure, should update to version 155.0.8059.79 or later to prevent potential exploitation. The vulnerability's impact is currently limited by the lack of reported exploitation and detailed information on affected versions and scope.

• Remote code execution inside the sandbox
• Potential for attacker exploitation of vulnerable Chrome browsers
• Need for Chrome browser updates to prevent exploitation
• Verification of Chrome browser version and patch status required

Technical summary

A use-after-free vulnerability in the PDF component of Google Chrome prior to version 155.0.8059.79 allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. The vulnerability is a high-severity issue that can be exploited by a remote attacker to execute arbitrary code inside the sandbox. Chrome users should update to version 155.0.8059.79 or later to prevent potential exploitation. The vulnerability's impact is currently limited by the lack of reported exploitation and detailed information on affected versions and scope.

Defensive priority

High priority for Chrome users to update to version 155.0.8059.79 or later.

Recommended defensive actions

• Update Google Chrome to version 155.0.8059.79 or later
• Review and monitor Chrome browser logs for suspicious activity
• Implement sandboxing and isolation measures for Chrome browser
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on potential exploitation. There is no evidence of active exploitation, but Chrome users should update as a precaution. The CVE record was published on 2026-10-13T21:01:47.602Z and has not been modified since then. The source item from cve_program_cvelist_v5 provides additional context on the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.