No attacks reportedCVE published · 6 Oct 2026
Google Chrome on macOS
CVE-2026-106378 Severity · High
CVSS 8.3
Affected
Chrome on Mac before 155.0.8059.39; Playwright 1.63.0 and earlier (Chromium 153.0.8010.12 or older); Puppeteer 25.12.0 and earlier (Chrome 154.0.8037.57 or older)
Fixed in
Chrome 155.0.8059.39/.40 for Mac; Playwright 1.64.0 (Chromium 156.0.8078.4); Puppeteer 25.13.0 (Chrome 155.0.8059.39)

CVE alert · AI and automation tools

CVE-2026-106378: Chrome's graphics process could type keystrokes and run programs on a Mac

An attacker who already controls part of Chrome can type keystrokes on a Mac and run programs outside the browser. Chrome on Mac before 155.0.8059.39 is affected, and so are older Playwright and Puppeteer browsers. Update Chrome, Playwright and Puppeteer today.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-106378 in Google Chrome on macOS, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-106378-chrome-macos/

What the alert says (facts checked 31 October 2026):
- Affected: Chrome on Mac before 155.0.8059.39; Playwright 1.63.0 and earlier (Chromium 153.0.8010.12 or older); Puppeteer 25.12.0 and earlier (Chrome 154.0.8037.57 or older)
- Fixed in: Chrome 155.0.8059.39/.40 for Mac; Playwright 1.64.0 (Chromium 156.0.8078.4); Puppeteer 25.13.0 (Chrome 155.0.8059.39)
- Exploited: No attacks reported as of 31 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where Google Chrome on macOS runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    npx playwright --version
    npx playwright install --list
    ls ~/Library/Caches/ms-playwright

    npm ls puppeteer
    npx @puppeteer/browsers list --path ~/.cache/puppeteer

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
ProductGoogle Chrome on macOS (web browser)
Affected versionsChrome on Mac before 155.0.8059.39; Playwright 1.63.0 and earlier (Chromium 153.0.8010.12 or older); Puppeteer 25.12.0 and earlier (Chrome 154.0.8037.57 or older)
Fixed inChrome 155.0.8059.39/.40 for Mac; Playwright 1.64.0 (Chromium 156.0.8078.4); Puppeteer 25.13.0 (Chrome 155.0.8059.39)
Severity8.3 High (CVSS 3.1, CISA ADP); Medium (Chromium security severity, Google, no CVSS score)
Who can attackRemote, no login. The victim must load a crafted web page, and the attacker must first take over a Chrome process with a separate bug.
ExploitedNo attacks reported as of 31 October 2026
CVE published6 October 2026

What an attacker can do

Chrome runs parts of itself inside a sandbox (a walled-off area that limits what code can touch). This flaw lets code in Chrome's GPU process (the part that draws graphics) step out of that sandbox on a Mac. The GPU process could send keystrokes to the desktop as if someone typed them. macOS accepted them when the app that launched Chrome held Accessibility permission (a macOS privacy setting that lets an app control the computer).

The researcher who found the flaw opened Spotlight and launched Calculator in a demo, and says the same path can open Terminal and run commands. Those commands run with the access of the person using the Mac, so the attacker can read files and customer data on it. They first need a separate bug to take over a Chrome process, and the victim must load a crafted web page. No attacks are reported as of 31 October 2026.

Who is affected

Google Chrome on Mac before 155.0.8059.39 is affected. The CVE record and NVD (the US National Vulnerability Database) list macOS only.

Playwright and Puppeteer, which developers use to control a browser from code, are affected when they run an old browser download. They use Chrome for Testing builds: Chrome versions made for automated tests that never update themselves. Playwright 1.63.0 bundles Chromium 153.0.8010.12 (the open-source base of Chrome) and Puppeteer 25.12.0 downloads Chrome 154.0.8037.57; earlier versions of both use older builds. Neither build contains the fix.

Playwright MCP lets AI assistants drive a browser. It uses the bundled Chromium when started with --browser chromium, with PLAYWRIGHT_MCP_BROWSER=chromium, or with a config file that sets browserName: 'chromium' and no channel. @playwright/mcp 0.0.82 and earlier bundle Chromium 154.0.8037.0 or older, without the fix.

The researcher says the escape works when the launching app has, or can request, Accessibility permission. In the demo, they launched Chrome from Terminal.

How to check your version

In Chrome, open the More menu, then Help, then About Google Chrome. It must show 155.0.8059.39 or later.

In each Playwright project, run:

shell
npx playwright --version
npx playwright install --list
ls ~/Library/Caches/ms-playwright

Playwright 1.63.0 or older is vulnerable; 1.64.0 and 1.64.1 are fixed. A chromium-NNNN folder numbered 1246 or lower lacks the fix (for example, chromium-1243 holds Chromium 153.0.8010.12). chromium-1247 holds Chromium 155.0.8059.12. That build already contains the code change that fixes the flaw, but it is below 155.0.8059.39, the version the CVE record names. chromium-1248 and later (Chromium 156.0.8078.4) are fixed. chromium_headless_shell-NNNN folders use the same numbers.

For Puppeteer, run:

shell
npm ls puppeteer
npx @puppeteer/browsers list --path ~/.cache/puppeteer

Puppeteer 25.12.0 or older is vulnerable; 25.13.0 or later is fixed.

For Playwright MCP, read the config of your MCP client (the AI assistant app that starts Playwright MCP). By default it uses the installed Google Chrome. It ships its own Playwright: read the @playwright/mcp version.

What to do now

Update Chrome on every Mac today. Open the More menu, then Help, then About Google Chrome, and click Relaunch.

Update Playwright to 1.64.0 or later, then download its browsers:

shell
npm install -D @playwright/test@latest
npx playwright install --with-deps

Update Puppeteer to 25.13.0 or later, then download the Chrome for Testing build it uses:

shell
npx puppeteer browsers install

Update to @playwright/mcp 0.0.83 or later (or use npx @playwright/mcp@latest in the MCP client config).

Playwright keeps an old build while an old project still needs it. Delete the cached browsers, then run the install commands again:

shell
npx playwright uninstall --all
npx @puppeteer/browsers clear --path ~/.cache/puppeteer

Last, open System Settings, then Privacy & Security, then Accessibility. Turn off apps that do not need it, such as terminals or editors that launch browsers. Do this in addition to the update. Google and the researcher published no official workaround and no signs of compromise.

Get help

Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.

AI agent and chatbot security audit

Can a message, an email or a document make your AI agent act against you? We try, and show you how to stop it.

From AED 35,000, excl. 5% VAT

Ask for a quote Book a call

Sources

  1. CVE-2026-106378 record CVE Program
  2. CVE-2026-106378 detail NIST NVD
  3. Stable Channel Update for Desktop (Tuesday, October 6, 2026) Google Chrome Releases
  4. CVE-2026-106378: Chrome GPU Sandbox Escape to RCE pwn.ai (PWNAI Research)
  5. Playwright v1.64.0 release notes Microsoft Playwright
  6. Puppeteer 25.13.0 release notes Puppeteer (Google)

The same update also fixes CVE-2026-106382, CVE-2026-106197, CVE-2026-106358, CVE-2026-106347.

More CVE alerts

All CVE alerts