
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-110171 is a use-after-free vulnerability in the Media component of Google Chrome that allows a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page. It was reported by security researcher Xinyang Ge on October 6, 2026, and publicly disclosed on October 13, 2026, as part of a broader Chrome stable channel update. The vulnerability affects Google Chrome versions prior to 155.0.8059.79 on Windows, Mac, and Linux. Google classifies this as High severity (Chromium security severity: High) (Chrome Releases, GitHub Advisory).
The vulnerability is classified as CWE-416 (Use After Free), occurring within Chrome's Media component (Chromium issue #570675082). A use-after-free flaw arises when a memory region is freed but a dangling pointer to that region is subsequently accessed, potentially allowing an attacker to control the freed memory and redirect execution flow. Exploitation requires a victim to visit or be redirected to a malicious HTML page that triggers the vulnerable Media code path, making the attack vector network-based with user interaction required. No additional authentication or privileges are needed on the victim's part beyond browsing to the attacker-controlled page (Chrome Releases, GitHub Advisory).
Successful exploitation allows a remote, unauthenticated attacker to execute arbitrary code within the Chrome sandbox process. While sandbox containment limits direct host OS access, code execution within the renderer process can serve as a stepping stone for sandbox escape chains when combined with additional vulnerabilities. Affected assets include any desktop system running a vulnerable version of Google Chrome on Windows, Mac, or Linux (Chrome Releases, Red Hat Bugzilla).
As of the disclosure date, there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation for CVE-2026-110171. The EPSS score is reported as 0.0, and the vulnerability has not been added to the CISA Known Exploited Vulnerabilities catalog. Bug details and links to the Chromium issue tracker (issue #570675082) remain restricted pending broad user adoption of the patch, which is standard Google practice to limit exploitation risk (GitHub Advisory, Chrome Releases).
Google has addressed this vulnerability in Chrome stable channel version 155.0.8059.79 (Linux) and 155.0.8059.79/.80 (Windows and Mac), released October 13, 2026. Users and administrators should update Chrome to version 155.0.8059.79 or later immediately via the browser's built-in update mechanism or enterprise deployment tools. Until patching is complete, organizations should consider restricting access to untrusted or unknown websites and implementing network-level controls to limit exposure to potentially malicious media content (Chrome Releases).
The vulnerability was disclosed as part of a large Chrome security update addressing 37 security fixes, which drew attention from the security community given the volume and severity of issues patched simultaneously. Red Hat tracked the issue via their Bugzilla system (Bug 2551980), indicating downstream Linux distribution maintainers are monitoring for impact on Chromium-based packages. No notable independent researcher commentary or significant social media discussion specific to CVE-2026-110171 has been identified beyond standard vulnerability tracking (Red Hat Bugzilla, Chrome Releases).
Fix availability across major Linux distributions and their releases.
bookworm
chromium: 155.0.8059.79-1~deb12u1
sid
chromium: 155.0.8059.79-1
trixie
chromium: 155.0.8059.79-1~deb13u1
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."