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:
- "Remote attacker": plan as if the attacker could be anywhere, not just in your building or on your Wi-Fi.
- "Specially crafted webpage": plan as if any page your team opens could be the trap. A link in an email, a fake invoice portal, an ad, a search result. Remind staff to be careful with unexpected links this week, but don't count on that alone; the update is the real fix.
- What the attacker could run: we wouldn't try to judge on your own how serious that is for your office. The browser is where your staff are logged into email, banking, billing and scheduling, so we'd simply treat this as urgent.
- "Google Chromium": our advice is to check every browser on your computers, including Microsoft Edge, and confirm each one has updated. If you're not sure whether a browser is affected, ask your IT provider or the browser's vendor rather than guessing.
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:
- A front-desk PC that's rarely turned off because it runs the scheduling screen all day.
- A few laptops that go home with staff and come back whenever.
- A shared "office manager" login on one machine, and personal browser profiles on others.
- An owner's laptop with dozens of tabs open that hasn't been restarted in a long time.
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
- On your computer, open Chrome.
- Open the browser's menu and find the About page for Chrome.
- Let it check. If it shows an update downloading, wait for it to finish.
- 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.
- Open the About page again. If you can't find the Relaunch option, you're on the latest version.
- For your records, open
chrome://versionand read the version number.
Microsoft Edge
- Open Edge and find the About page in its menu.
- Let it check and install, then restart the browser when it asks.
- Open
edge://versionand 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:
| Computer | User / location | Browser | Version after relaunch | Checked by | Date |
|---|---|---|---|---|---|
| FRONT-DESK-1 | Reception | Chrome | (copy from chrome://version) | Office manager | 11/12 |
| FRONT-DESK-1 | Reception | Edge | (copy from edge://version) | Office manager | 11/12 |
| LAPTOP-OWNER | Owner (remote) | Chrome | (copy from chrome://version) | Owner | 11/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.
- Morning huddle (5 minutes): the office manager tells everyone the browser will restart at lunch and that Chrome reopens saved tabs and windows automatically after it restarts.
- Lunch (20โ30 minutes total): each person runs the About-page check on their own machine and relaunches. The office manager walks the room with the log and fills in the version from
chrome://versionandedge://version. - Laptops that are offsite: the owner texts the steps; staff reply with a screenshot of the About page.
- End of day: one machine still showing an older version? Flag it for follow-up rather than leaving it, and check whether the browser was ever fully closed or whether updates have been switched off.
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:
- Leave updates enabled for all users, and don't let individuals turn them off.
- Set a relaunch reminder or a relaunch window, so a browser can't keep running an old version for weeks. Pick a time that fits your day, like after close or during lunch.
- Do the same for Edge. Ask your IT provider to set Edge's update and restart behaviour to match.
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
- Assuming an update means you're covered. Downloaded isn't running. The new version only runs after the browser is relaunched.
- Only updating one browser. Check Edge too, even on machines where nobody thinks they use it.
- Forgetting the laptops that go home. Put those laptops at the top of your list.
- Old web apps used as an excuse. When an outdated browser is the only way into a supplier's portal, push the supplier to fix it rather than leaving every PC exposed.
- Shared machines with extra browsers. Any extra browser someone added to a shared PC needs its own check.
- No record. Write down what you checked and when, so you can show it later.
What we'd do if this were our office
If you asked us what to do this week, here's the order:
- Today: relaunch every browser on every machine and run the About-page check. Fill in the log.
- This week: confirm auto-update is on for every browser on every machine, and make sure nobody can turn it off.
- This month: set up central management for browser updates and a relaunch window, plus one inventory screen that shows every machine's version.
- 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
- [ ] Every Chrome and Edge window closed and reopened today
- [ ] About page checked on every machine, with no relaunch option left showing
- [ ] Every browser's version number written in the log
- [ ] Laptops working away from the office checked as well
- [ ] Any other browsers found and updated
- [ ] Auto-update confirmed on for every browser
- [ ] A regular relaunch or restart rule in place
- [ ] Someone (or something) watching the CISA KEV catalog for the tools you use
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
- CISA โ Known Exploited Vulnerabilities Catalog (November 12, 2026)
- CISA โ CISA Adds Six Known Exploited Vulnerabilities to Catalog (November 10, 2026)
- CISA โ Known Exploited Vulnerabilities Catalog (November 10, 2026)
- Google โ Manage Chrome updates (Windows) - Chrome Enterprise and Education Help (November 12, 2026)
- Google Chrome Enterprise Help โ Manage Chrome updates (Windows) (November 12, 2026)
- Google Chrome Help โ Update Google Chrome (November 12, 2026)
- BleepingComputer โ Google patches fifth Chrome zero-day bug exploited in attacks this year (June 9, 2026)
- SecurityWeek โ Google patches 6th Chrome zero-day of 2026 (September 4, 2026)
- SOC Prime โ CVE-2026-125350: Chrome XML Zero-Day Exploited in the Wild (November 10, 2026)
- Threat Defence โ Chrome CVE-2026-125350 Zero-Day: Patching and Hunting (November 10, 2026)