Short answer: update and relaunch Chrome and Edge on every office computer today. Updating takes a couple of minutes per machine. Don't stop at the download: Chrome downloads updates on its own, but the new version only runs after the browser is relaunched.

Below is what the bug does in plain words, a two-minute check you can run at the front desk or on a laptop, and how we'd set things up so you never have to chase a browser patch by hand again.

What happened, in plain words

CISA maintains the Known Exploited Vulnerability (KEV) catalog as the authoritative source of vulnerabilities that have been exploited in the wild. Our take: when a product you use shows up there, treat it as a "this week" job, not a "someday" job.

You can search the CISA KEV catalog yourself to see the current entry.

How we'd suggest a busy owner read that entry:

The timeline was fast. Reporting says the bug was reported anonymously to Google on November 6, 2026, and Google confirmed on November 9 that an exploit for the vulnerability exists in the wild. That is a short window, which is why we'd act today rather than waiting for the next routine maintenance day.

This keeps happening

This isn't a one-off. In June, Google said it was aware that an exploit for CVE-2026-11645 exists in the wild. In September, an exploit for CVE-2026-85046 was reported to exist in the wild, and Google said it was aware that an exploit for CVE-2026-87491 exists in the wild. Each time, our advice is the same boring step: get the update onto every machine and relaunch the browser. A machine that's never restarted deserves extra attention in your check.

Google Chrome can automatically update when a new version of the browser is available on your device, but the new version only runs after the browser is relaunched. Treat a browser that's never closed as a browser that may not be patched. :::

Why this matters for a small office specifically

Larger organisations may have dedicated staff and tooling for this. A small office often doesn't, so it helps to picture where the gaps could be.

Hypothetical: a small office might have something like this:

Any of those could be a browser that has downloaded the fix but isn't running it yet. And machines like these often touch money and client data: the scheduling system, the billing portal, the bank.

Our view: this guidance is worth following even for a business your size. Under BOD 26-04, all federal civilian executive branch (FCEB) agencies are required to remediate vulnerabilities in the KEV catalog within prescribed timeframes. CISA encourages all organizations, not only federal agencies, to adopt risk-based vulnerability management and prioritize remediation of KEV catalog vulnerabilities. It also says organizations should use the KEV catalog as an input to their vulnerability management prioritization framework. For a small office, our suggestion is to keep that "framework" simple: if it's on that list and we use it, we patch it this week.

If you're in a regulated line of work, keep a record of what you checked and when. Our view is that being able to say "we checked every machine on the 12th, here's the list" puts you in a much better position than "I think so" if a client, insurer or auditor ever asks.

The 2-minute check: is this computer patched?

Do this on every computer that has a browser installed, including laptops that are currently at someone's house (send them these steps).

Chrome

  1. On your computer, open Chrome.
  2. Open the browser's menu and find the About page for Chrome.
  3. Let it check. If it shows an update downloading, wait for it to finish.
  4. To apply any available updates, click Relaunch. Chrome saves your opened tabs and windows and reopens them automatically when it restarts. Tell your team that up front, so nobody puts the relaunch off for fear of losing work.
  5. Open the About page again. If you can't find the Relaunch option, you're on the latest version.
  6. For your records, open chrome://version and read the version number.

Microsoft Edge

  1. Open Edge and find the About page in its menu.
  2. Let it check and install, then restart the browser when it asks.
  3. Open edge://version and note the version number.

Other browsers

If anyone uses another browser, do the same: find About in the menu, update, relaunch. If you're not sure what's installed on a machine, look at the taskbar and the Start menu. Check every machine rather than assuming everyone uses the same browser you do.

Google's help page says updates normally happen in the background when you close and reopen your computer's browser. Then spot-check the About page on each machine. :::

Write it down

A simple log turns a scramble into proof. Here's the format we'd use:

ComputerUser / locationBrowserVersion after relaunchChecked byDate
FRONT-DESK-1ReceptionChrome(copy from chrome://version)Office manager11/12
FRONT-DESK-1ReceptionEdge(copy from edge://version)Office manager11/12
LAPTOP-OWNEROwner (remote)Chrome(copy from chrome://version)Owner11/12

Once every row matches the newest version you saw on a fully updated machine, you're done with this round.

A worked example

Hypothetical: a dental office with six front-office and operatory PCs, two hygienist laptops and the owner's laptop. Nine machines, each with Chrome and Edge.

The point isn't the exact minutes. The point is that a small office can aim to verify every machine in one lunch break, without buying anything.

Make browser updates automatic from now on

Checking by hand works for this week. It doesn't work as a system, and we'd plan on there being a next time. Here's how we'd set things up so updates happen without anyone remembering.

1. Keep auto-update on, everywhere

Google recommends that admins keep auto-updates turned on so that users receive critical security fixes and new features as they become available. If your office turned updates off at some point because an old web app broke, our advice is to deal with that app, not to leave every browser frozen.

2. Manage Chrome centrally if you're on Windows

As a Microsoft Windows administrator, you can use Google Update to manage how your users' Chrome browser and Chrome apps are updated. Our advice for small offices:

3. Use one inventory, not memory

Whatever tool you or your IT provider use, the goal is a single screen that shows every computer and the browser version it's running. When the next browser bug lands on the KEV list, you look at one list instead of walking the office.

4. Make "relaunch" a habit

Set a simple rule: browsers fully close at the end of the day, or computers restart regularly.

5. Watch the KEV list, or have someone watch it for you

CISA says organizations should use the KEV catalog as an input to their vulnerability management prioritization framework. You don't need to read it daily. You need someone, or something, that tells you when a product you actually use shows up on it. That's a good small job for automation: a simple watcher that checks the catalog and sends your office manager a text when Chrome, Edge, Windows or your main business apps appear. If you want help building one, see our AI automation services.

Common pitfalls to avoid

What we'd do if this were our office

If you asked us what to do this week, here's the order:

  1. Today: relaunch every browser on every machine and run the About-page check. Fill in the log.
  2. This week: confirm auto-update is on for every browser on every machine, and make sure nobody can turn it off.
  3. This month: set up central management for browser updates and a relaunch window, plus one inventory screen that shows every machine's version.
  4. Ongoing: a lightweight KEV watcher so the next one shows up as a text message, not as a news headline you see days late.

This is mainly a settings job, not a shopping trip. The hard part usually isn't the technology; it's knowing which settings matter and having time to set them once, properly.

Checklist: Chrome and Edge zero-day response

Next step

If you'd like a hand setting up central browser updates or a KEV watcher, talk to us about an AI consultation for small business IT and automation. We'll look at how your office computers get updated today, where the gaps are, and what it would take to make patching automatic and provable. We work with offices across Southern California.

Start with a Free Automation Audit. We'll tell you plainly what's worth automating and what isn't.

Sources