On November 9, 2026, Google fixed a Chrome flaw that attackers are exploiting right now, tracked as CVE-2026-125350. An employee only has to open a specially crafted web page for the attacker to run code inside the browser, with no file download and no extra click. The fix today is simple: open Chrome on every company device, type chrome://settings/help in the address bar, confirm the version is 158.0.8127.36 or later, then click «Relaunch». Version 157.0.8103.50 is the minimum that closes this flaw, but Google has since shipped two more updates fixing 287 other vulnerabilities.
This article complements our piece on the exploited Outlook flaw and the Office update: that one is about a file arriving by email, this one is about a page opening in the browser.
What exactly is the flaw?
According to Google's official announcement on the Chrome Releases blog, the November 9 update moved Chrome to 157.0.8103.50/.51 on Windows and Mac and 157.0.8103.50 on Linux, with 9 security fixes. The most serious is CVE-2026-125350, a «use after free» memory flaw in the XML component, rated High. Google wrote plainly that it is aware an exploit for this flaw exists «in the wild», meaning in real attacks, not in a lab.
The description in the US National Vulnerability Database (NVD) spells out the risk: in Chrome versions before 157.0.8103.50, the flaw lets a remote attacker execute arbitrary code inside the browser sandbox via a crafted HTML page. In practice, a link in a WhatsApp message or a compromised ad on an ordinary website could be enough to start the attack.
On November 10, the US cybersecurity agency CISA added the flaw to its Known Exploited Vulnerabilities catalog and gave US government agencies until November 24 to fix it. That deadline does not legally bind Saudi companies, but it is a sensible benchmark: an exploited flaw gets closed in days, not weeks. According to BleepingComputer, it is the eighth exploited Chrome zero-day of 2026.
Why «Chrome updates itself» is not enough
Chrome downloads updates automatically, but it does not apply them until the browser is relaunched. An employee who keeps Chrome open for weeks with dozens of tabs stays on the old version the whole time. On top of that, Google itself writes in every announcement that the update «will roll out over the coming days/weeks», so not every device receives it on the same day.
Updates have come quickly this month. Here is the timeline from Google's official blog:
- November 3: Chrome 157 with 212 security fixes.
- November 9: version 157.0.8103.50 with 9 fixes, including the exploited flaw.
- November 11: version 157.0.8103.78/.79 with 83 fixes, 5 of them rated Critical.
- November 17: Chrome 158 (158.0.8127.36/.37) with 204 security fixes.
That is 508 security fixes in 15 days. So do not settle for the minimum: make version 158 your target.
Today's steps in 4 points
- Office computers: on every Windows, Mac or Linux machine, open chrome://settings/help, wait for the download to finish, then click «Relaunch». Tabs come back as they were.
- Phones: update Chrome from Google Play or the App Store. Android version 158.0.8127.42 was released on November 17 and carries the same security fixes as the desktop release.
- Other browsers: Edge, Brave and Opera are built on the same Chromium engine, and each receives the fix in its own update. Open the «About» page of every browser your team uses and update it.
- If your devices are managed: ask your IT administrator to enable the RelaunchNotification policy together with RelaunchNotificationPeriod, so Chrome forces the employee to relaunch within a period you set instead of leaving the update pending.
How do you confirm the whole company is updated?
In a small company, ask each employee for a screenshot of chrome://settings/help showing the version number and collect them in one sheet. Five minutes is enough for ten devices. In larger companies, the Chrome Enterprise admin console or your device management tool (such as Intune) shows the Chrome version on each device, so ask for a report of the devices still below 157.0.8103.50 and start with those.
Watch out for forgotten devices: the reception PC, the cashier machine that opens the dashboard in a browser, and staff personal devices used to sign in to company email. These are usually the last to be updated and the first to be breached.
What if you suspect a device opened a malicious page?
Google has not published details of the attacks or indicators that reveal them, so there is no confirmed sign to look for. The reasonable response: update the browser immediately, scan the device with your security software, change the passwords of accounts saved in that browser, and turn on two-step verification for email and financial systems if it is not already on.
The Origami view
The browser is now the workplace itself: email, invoices, store dashboards and cloud systems all open inside it. A flaw in Chrome is a door to all of that. Our advice to businesses is to make «relaunch the browser» a weekly habit and to give one person responsibility for tracking browser and operating system updates. If you want web systems that do not depend on the user's luck, you can contact the Origami team to review your setup.
Sources
- Google: Chrome update of November 9, 2026 and the exploited flaw CVE-2026-125350
- Google: Chrome update of November 11, 2026 (83 security fixes)
- Google: Chrome 158 release, November 17, 2026 (204 security fixes)
- Google: Chrome 158 for Android
- NVD: description of CVE-2026-125350
- CISA: Known Exploited Vulnerabilities catalog
- Chrome Enterprise: RelaunchNotification policy
- BleepingComputer: Google patches eighth Chrome zero-day exploited in 2026
Frequently asked questions
How do I know Chrome on my computer is updated?
Type chrome://settings/help in the address bar. The version should be 157.0.8103.50 or later to close the exploited flaw, and ideally 158.0.8127.36 or later. If a «Relaunch» button appears, the update has downloaded but is not applied yet.
Is it enough that employees don't download files from the internet?
No. According to the NVD description, the browser only has to open a crafted HTML page for the attacker to run code, with no file download. Updating is the only confirmed protection.
We use Microsoft Edge, not Chrome. Are we safe?
Edge is built on the same Chromium engine and receives the fix in its own update. Open edge://settings/help, make sure it is updated and relaunch it, and do the same for Brave and Opera.
What is the November 24 deadline, and does it bind Saudi companies?
It is the date the US agency CISA set for its government agencies to fix the flaw, and it does not legally bind Saudi companies. It is still a good benchmark: an actively exploited flaw should be closed within days.







