Google vulnerabilities

CVE-2026-13789 Critical · 9.6 CWE-416 Jun 30, 2026

Google Chrome GPU Use-After-Free with Possible Sandbox Escape (CVE-2026-13789)

Use after free in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

CVE-2026-13788 High · 8.8 CWE-416 Jun 30, 2026

Use after free in Fullscreen in Google Chrome on Android prior to 150.0.7871.47 allowed a remote...

Use after free in Fullscreen in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13787 High · 8.1 CWE-416 Jun 30, 2026

Use after free in Chromoting in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote...

Use after free in Chromoting in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Critical)

CVE-2026-13786 High · 8.8 CWE-416 Jun 30, 2026

Use after free in Ozone in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to...

Use after free in Ozone in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13785 Critical · 9.6 CWE-416 Jun 30, 2026

Google Chrome for Mac: Bluetooth use-after-free enabling possible sandbox escape

Use after free in Bluetooth in Google Chrome on Mac prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13784 High · 8.8 CWE-416 Jun 30, 2026

Use after free in Views in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who...

Use after free in Views in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13783 High · 8.8 CWE-416 Jun 30, 2026

Use after free in Views in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who...

Use after free in Views in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13782 Critical · 10.0 CWE-416 Jun 30, 2026

Google Chrome Browser Use-After-Free Enabling Sandbox Escape

Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13781 Critical · 9.6 CWE-20 Jun 30, 2026

Google Chrome Skia Improper Input Validation Enabling Sandbox Escape

Insufficient validation of untrusted input in Skia in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13780 Critical · 9.6 CWE-20 Jun 30, 2026

Google Chrome ANGLE Insufficient Input Validation Enabling Sandbox Escape (CVE-2026-13780)

Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13779 High · 8.1 CWE-416 Jun 30, 2026

Use after free in Chromoting in Google Chrome on ChromeOS prior to 150.0.7871.47 allowed a remote...

Use after free in Chromoting in Google Chrome on ChromeOS prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Critical)

CVE-2026-13778 High · 7.8 CWE-416 Jun 30, 2026

Use after free in WebUSB in Google Chrome on Mac prior to 150.0.7871.47 allowed a local attacker...

Use after free in WebUSB in Google Chrome on Mac prior to 150.0.7871.47 allowed a local attacker to execute arbitrary code via a malicious peripheral. (Chromium security severity: Critical)

CVE-2026-13777 High · 8.8 CWE-20 Jun 30, 2026

Improper Input Validation in Google Chrome

Insufficient validation of untrusted input in iOSWeb in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13776 Critical · 9.8 CWE-843 Jun 30, 2026

Google Chrome Dawn type confusion (CVE-2026-13776)

Type Confusion in Dawn in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13775 Critical · 9.8 CWE-416 Jun 30, 2026

Google Chrome GPU Use-After-Free Sandbox Escape (CVE-2026-13775)

Use after free in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13774 High · 8.1 CWE-416 Jun 30, 2026

Use after free in Extensions in Google Chrome prior to 150.0.7871.47 allowed an attacker who...

Use after free in Extensions in Google Chrome prior to 150.0.7871.47 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. (Chromium security severity: Critical)

CVE-2026-11720 Critical · 9.1 CWE-22 Jun 29, 2026

Path Traversal in googleapis/mcp-toolbox HTTP Tool URL Builder

A path traversal vulnerability exists in the HTTP tool URL builder of googleapis/mcp-toolbox. When constructing downstream API requests, the URL builder substitutes user-controlled pathParams into the configured tool path and parses the resulting string as a relative URL. While it checks that the input does not alter the scheme, host, or user info, it relies on ResolveReference for the final URL resolution. Because dot segments (../) are normalized during this resolution step, an attacker can supply path parameters containing directory traversal sequences to escape the operator-configured path scope. This allows the client to coerce the toolbox into making requests to unintended endpoints on the same target host while forwarding the toolbox's configured credentials (e.g., bypassing a restricted path like /api/v1/users/{{.id}} to reach /admin/secrets).

CVE-2026-13283 High · 7.5 CWE-416 Jun 25, 2026

Use after free in AdFilter in Google Chrome on Android prior to 149.0.7827.201 allowed a remote...

Use after free in AdFilter in Google Chrome on Android prior to 149.0.7827.201 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

CVE-2026-13282 Medium · 6.8 CWE-416 Jun 25, 2026

Use after free in Payments in Google Chrome on Android prior to 149.0.7827.201 allowed a local...

Use after free in Payments in Google Chrome on Android prior to 149.0.7827.201 allowed a local attacker to potentially exploit heap corruption via physical access to the device. (Chromium security severity: High)

CVE-2026-13281 High · 8.3 CWE-472 Jun 25, 2026

Integer overflow in Mojo in Google Chrome prior to 149.0.7827.201 allowed a remote attacker who...

Integer overflow in Mojo in Google Chrome prior to 149.0.7827.201 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

CVE-2026-53766 Medium · 6.1 CWE-22 Jun 24, 2026

chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textually falls under one of the configured root paths. path.resolve() does not canonicalize symbolic links. As a result, a symlink inside a configured workspace root can point to a file outside that root, pass validation, and then be followed by downstream file read/write operations. This bypass applies even when the MCP client correctly declares the roots capability with a non-empty list. It is separate from the documented legacy behavior where missing roots capability allows all paths. The practical impact is a workspace-boundary bypass. In the write direction, filePath-writing tools can overwrite out-of-root files through an in-root symlink. In the read direction, upload_file can read through the symlink and send the file to the currently selected web page. This vulnerability is fixed in 1.1.0.

CVE-2026-53765 Medium · 6.1 CWE-59 Jun 24, 2026

chrome-devtools-mcp: daemon.pid write follows symlinks in /tmp fallback runtime directory

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.20.0 until 1.1.0, The chrome-devtools-mcp daemon writes its PID file with fs.writeFileSync() to a deterministic runtime path. On typical macOS environments, and on Linux sessions where $XDG_RUNTIME_DIR is unset, that runtime path falls back to /tmp/chrome-devtools-mcp-<uid>/daemon.pid. Because the write does not use O_NOFOLLOW, a local low-privilege user on the same POSIX host can pre-create /tmp/chrome-devtools-mcp-<victim_uid>/daemon.pid as a symlink to a file writable by the victim. When the victim later starts daemon mode, fs.writeFileSync() follows the symlink and truncates the target file to the daemon PID string. This vulnerability is fixed in 1.1.0.

CVE-2026-11998 High · 7.6 CWE-791 Jun 24, 2026

AngularJS XSS via SCE resource URL sanitization bypass

A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session. SCE's purpose is to ensure that only trusted or safe values are used in certain security-sensitive contexts, such as resource URLs, including URLs that define executable JavaScript scripts, '<iframe>' documents, route templates, etc. A flaw in the logic that tries to match entire URLs against regular expression matchers can result in partial matches for certain types of regular expressions, effectively bypassing the policies and allowing the use of unsafe values as resource URLs. This issue affects AngularJS versions greater than or equal to 1.2.0-rc.3. Note: The AngularJS project was already End-of-Life when this CVE was published and will not receive any updates to address this issue. For more information see the End-of-Life announcement https://docs.angularjs.org/misc/version-support-status .

CVE-2026-13038 High · 8.8 CWE-416 Jun 24, 2026

Use after free in Autofill in Google Chrome on Windows prior to 149.0.7827.197 allowed a remote...

Use after free in Autofill in Google Chrome on Windows prior to 149.0.7827.197 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

CVE-2026-13037 High · 7.8 CWE-416 Jun 24, 2026

Use after free in WebView in Google Chrome on Android prior to 149.0.7827.197 allowed a local...

Use after free in WebView in Google Chrome on Android prior to 149.0.7827.197 allowed a local attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)