Picked
Chrome flaw used in attacks: update and relaunch today
- Why it matters
- Attackers are already using a flaw in Google Chrome (CVE-2026-125350) on Windows, Mac and Linux. Google fixed it in Chrome 157.0.8103.50, but the fix only takes effect after Chrome is closed and reopened.
- What we're doing
- We're confirming Chrome is updated and relaunched on the computers we manage. If your team uses Chrome on computers we don't manage, the steps below take about a minute per computer.
- What you should do
- On every computer, open Chrome's About page, let it update to 157.0.8103.50 or later, and click Relaunch. Then update Microsoft Edge and any other Chrome-based browser the same way.
What's going on
Chrome updates itself in the background, but a downloaded update doesn't protect you until the browser restarts, and many people leave Chrome open for days or weeks. Because attackers are already using this flaw, it's worth checking today rather than waiting for Chrome to restart on its own. Microsoft Edge, Brave and other browsers built on Chrome's engine get their own fixes on their own schedules, so check them too.
How to check
- Open Google Chrome.
- Click the three-dot menu (⋮) in the top-right corner of the window. On a Mac you can also use the Chrome menu at the top of the screen.
- Choose Help, then About Google Chrome.
- Look at the version number. 157.0.8103.50 or higher means the fix is installed.
How to fix it
- Stay on the About Google Chrome page. Chrome checks for the update and downloads it on its own.
- When the Relaunch button appears, save anything you're working on and click Relaunch. Chrome reopens your tabs.
- Open About Google Chrome again and confirm the version is 157.0.8103.50 or later.
- Using Microsoft Edge too? Open its menu (…), choose Help and feedback, then About Microsoft Edge, and restart it the same way.
- Responsible for several computers? Ask your IT provider to confirm every one is updated and has been restarted.
Deeper dive: check from the command line
Optional, for readers comfortable with a command line. These commands only read information; they don't change, install or delete anything. Run them only on computers and websites you own or are responsible for. Results depend on how a computer is set up, so a clean result isn't a guarantee. If something looks wrong, or you're not sure what you're seeing, stop and call your IT provider. Provided as-is, for information.
Windows (PowerShell): which Chrome version is installed
(Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe","${env:ProgramFiles(x86)}\Google\Chrome\Application\chrome.exe" -ErrorAction SilentlyContinue).VersionInfo.ProductVersionWhat you should see: A version number. 157.0.8103.50 or higher means the fixed version is installed. No output means Chrome isn't in the usual place; use the About page instead.
Windows (PowerShell): when Chrome was last started
Get-Process chrome -ErrorAction SilentlyContinue | Sort-Object StartTime | Select-Object -First 1 StartTimeWhat you should see: The time Chrome was opened. If that's before the update was installed, the old version is still running, so relaunch Chrome. No output means Chrome isn't open.
Mac (Terminal): which Chrome version is installed
defaults read "/Applications/Google Chrome.app/Contents/Info" CFBundleShortVersionStringWhat you should see: A version number such as 157.0.8103.51. 157.0.8103.50 or higher means the fixed version is installed.
Mac (Terminal): when Chrome was last started
ps -o lstart= -p "$(pgrep -x 'Google Chrome' | head -1)"What you should see: The date and time Chrome was opened. If that's before the update arrived, relaunch Chrome. An error or no output means Chrome isn't running.
Linux (terminal): which Chrome version is installed
google-chrome --versionWhat you should see: Something like "Google Chrome 157.0.8103.50". That version or higher means you're fixed.