All CVEs — page 283 of 631
The complete archive, 25 per page, newest first. 15775 records. Search instead.
A privilege escalation vulnerability in Chrome's sandbox on macOS allows remote attackers to execute arbitrary code outside the sandbox after compromising the renderer process. This creates a significant security risk as it breaks the core sandboxing protection that isolates browser processes.
A race condition in Google Chrome's font handling allows a compromised renderer process to execute arbitrary code outside the sandbox, potentially leading to full system compromise. This vulnerability is particularly dangerous because it can be exploited remotely and leverages a pre-compromised state.
This flaw involves incomplete cleanup in Dawn, the rendering engine of Google Chrome prior to version 155.0.8059.39, allowing remote attackers to execute arbitrary code outside the sandbox via a crafted HTML page.
A type confusion vulnerability in V8 of Google Chrome prior to 155.0.8059.39 could allow a remote attacker to execute arbitrary code within the sandbox by tricking a user into visiting a crafted HTML page.
This flaw involves a use after free vulnerability in the Fonts component of Google Chrome on Windows, allowing remote attackers to execute arbitrary code within a sandbox via a crafted HTML page. This is significant because it can lead to privilege escalation and unauthorized code execution.
This flaw in Google Chrome prior to 155.0.8059.39 allows remote attackers to execute arbitrary code outside the sandbox via a crafted HTML page, posing a significant security risk.
This flaw in Google Chrome on Android allows a remote attacker to obtain sensitive information via a crafted HTML page due to incorrect authorization in the Transactions Platform. This matters because it can lead to unauthorized data access.
A missing authorization check in Google Chrome's mobile browser on Android allowed attackers to execute arbitrary code outside the sandbox through a co-installed app, potentially leading to full system compromise.
Chrome's FullScreen API had a missing authorization check that allowed attackers with compromised renderer processes to bypass system access restrictions through crafted HTML pages, potentially enabling unauthorized access to system resources.
This flaw involves a use-after-free vulnerability in the Navigation component of Google Chrome prior to 155.0.8059.39, allowing remote attackers to execute arbitrary code outside the sandbox via a crafted HTML page.
This flaw involves a use-after-free vulnerability in WebRTC within Google Chrome prior to 155.0.8059.39, allowing remote attackers to execute arbitrary code within a sandboxed environment.