Selkey Cyber Security Pvt Ltd blog cover: Google Patches Chrome Zero-Day: Eighth of 2026

Google pushed out a Chrome security update this week that fixes nine vulnerabilities, including one that attackers were already using against real users (The Hacker News). The bug, tracked as CVE-2026-125350, is the eighth actively exploited Chrome zero-day that Google has had to patch since January, a run that says a lot about how often attackers are finding fresh ways into the world’s most used browser.

For most people the fix is simple: let Chrome update itself. For IT teams managing dozens or hundreds of company laptops, this is the kind of update that needs to go out everywhere, not just wherever an employee happens to click “relaunch” on a browser prompt.

What the vulnerability actually does

The flaw, CVE-2026-125350, carries a CVSS score of 8.8 and sits in Chrome’s XML component. It is a use-after-free bug, a type of memory error where the browser tries to use a piece of data after it has already been freed, which attackers can exploit to run their own code inside Chrome’s sandbox. All it takes is a specially crafted HTML page (The Hacker News), meaning a user does not need to download anything or click a suspicious link beyond simply opening the wrong page.

An anonymous security researcher reported the bug to Google on 6 November 2026, and Google moved quickly to ship a fix (The Hacker News).

The eighth zero-day of a busy year

This is the eighth Chrome zero-day that Google has confirmed was being actively exploited before a patch existed, all within 2026 (SecurityWeek). Eight in under eleven months is a steady pace, and it points to how much attacker attention is focused on browsers rather than operating systems or servers, simply because so much of daily work and banking now happens inside a browser tab.

In India, Chrome is the default browser on most office laptops, bank branch systems and several government portals. A single employee opening a booby-trapped page on an unpatched machine is enough to give an attacker a foothold inside the sandbox, and from there the risk depends on what else that machine can reach, whether that is an internal file share, a UPI merchant dashboard or a customer database.

CISA’s deadline and why it matters beyond the US

The US Cybersecurity and Infrastructure Security Agency, CISA, has added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog, giving US federal agencies until 24 November 2026 to apply the fix (The Hacker News). That deadline only legally binds US government bodies, but it is a useful signal for everyone else: when CISA lists a bug this way, it generally means there is real evidence of exploitation in the wild, not just a theoretical risk. Indian businesses do not need to wait for a CERT-In advisory to treat that signal seriously.

What to do now

The fix itself is already available, so the main job now is making sure it actually reaches every device.

  • Open Chrome’s menu, go to Settings, then About Chrome, and let it check for and install the latest update, then relaunch the browser
  • IT and security teams should push the update through device management tools to every company laptop and desktop rather than waiting for individual users to click the in-browser prompt
  • Watch for unusual Chrome crashes or unexpected outbound network connections in the days after visiting an unfamiliar site, since these can be signs that something tried to exploit the browser before it was patched

None of this needs specialised tools or a deep security background. It is the same habit that protects against most browser based attacks: keep the software current and treat update prompts as something to act on the same day, not the same month.

Frequently asked questions

What is CVE-2026-125350?

It is a Chrome vulnerability with a CVSS score of 8.8, caused by a use-after-free bug in Chrome’s XML component that lets attackers run code inside the browser’s sandbox through a crafted HTML page. Google patched it this week after confirming it was already being used in attacks.

How do I check if my Chrome browser is updated?

Open Chrome, go to Settings, then About Chrome. If an update is available it will install automatically, and you just need to click relaunch for it to take effect.

Was this Chrome flaw actually exploited before the patch?

Yes. Google confirmed active exploitation, and CISA added the vulnerability to its Known Exploited Vulnerabilities catalog with a federal remediation deadline of 24 November 2026.

Why does Google keep finding zero-days in Chrome?

Chrome’s huge user base makes it a constant target, and this is already the eighth actively exploited zero-day Google has had to patch in 2026 alone.

Chrome zero-days are becoming a regular fixture of 2026, and the response stays the same each time: update promptly and push the fix to every device your business depends on.

Talk to our experts

If you want a second pair of eyes on your own security, the Selkey Cyber Security Pvt Ltd team is happy to talk. You can call +91 7490 999 564 or +91 7777 999 564, email hello@selkeycybersecurity.com or visit www.selkeycybersecurity.com.

Sources