Google Chrome Beta (EXE)
Last updated
Try new features with Chrome Beta
Install with winget
$ winget install --id Google.Chrome.Beta.EXE --exact --version 156.0.8078.17Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.
For Intune admins
Stop chasing app updates. Pckgr patches them for you.
Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph - no manual repackaging, no chasing vendor sites.
Start free 30-day trialFrom $49/month. No credit card required.
Not on Intune? Pckgr RMM deploys and patches apps like this one on any Windows fleet. Free for up to 5 devices.
About
Feeling adventurous? Preview upcoming Google Chrome features before they’re released and give us feedback to make Chrome a better browser.
Installers · v156.0.8078.17
| Architecture | Type | Scope | Install | Download |
|---|---|---|---|---|
| x86 | EXE | user | Direct | |
| x86 | EXE | machine | Direct | |
| x64 | EXE | user | Direct | |
| x64 | EXE | machine | Direct | |
| arm64 | EXE | user | Direct | |
| arm64 | EXE | machine | Direct |
Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.
Security
25 known CVEs via NVD
Confused deputy in Mobile in Google Chrome on on iOS prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions into a privileged page via a crafted HTML page. (Chromium security severity: Low)
Race condition in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Missing authorization in BrowserTag in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)
Information leak in Audio in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted Chrome extension. (Chromium security severity: Medium)
Use after free in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Incorrect authorization in API in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low)
Use after free in PDF in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Incorrect calculation in API in Google Chrome on on Windows prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to spoof UI elements via a crafted Chrome extension. (Chromium security severity: Medium)
See a CVE that affects your fleet? Push the patched version to Intune in one click with Pckgr - automated patching is the only way to keep up.
Not on Intune? Patch it with Pckgr RMM, free for up to 5 devices.
Related apps
More from Google LLC or browse browser, chromium, internet.
Frequently asked questions
How do I install Google Chrome Beta (EXE) on Windows?
How do I install Google Chrome Beta (EXE) silently for unattended deployment?
How do I uninstall Google Chrome Beta (EXE) via winget?
Is Google Chrome Beta (EXE) free?
Does Google Chrome Beta (EXE) work on Windows 10?
How do I keep Google Chrome Beta (EXE) up to date?
Recent versions
- 156.0.8078.17latest
- 156.0.8078.16
- 156.0.8078.4
- 155.0.8059.12
- 155.0.8059.5
- 154.0.8037.17
- 154.0.8037.0
- 153.0.8010.12
- 153.0.8010.5
- 152.0.7977.54