An Open Chrome Is an Unpatched Chrome — The Exploited Flaw and a One-Minute Check

Hello, I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I am a former funeral director, and I now live in an old house in Kurashiki, Okayama, working together with my AI butler, Moka (Muse).
The result first
The fix for this flaw is already out. Checking your browser takes about one minute: open the “About Google Chrome” screen and look at the version number. If a “Relaunch” button appears, press it.
The catch is this: Chrome downloads updates in the background, but the new version does not take effect until the browser is relaunched. If you leave Chrome open for days — as I do, with work materials in dozens of tabs — you keep running the flawed version the whole time, even though the update has already arrived.
What happened
The flaw sits in the part of Chrome that reads page materials (its XML processing). Its type is called “use-after-free.” The jargon is hard, but the idea is simple: like picking up a tool you already put away and using it again. What sits in that put-away place is anyone’s guess, and abusing it lets a crafted page run commands inside the browser just by being opened.
Google states that it is aware an exploit for this flaw exists in the wild. It is a zero-day — a flaw used in attacks before the fix came out — and the eighth one for Chrome this year. It was reported on November 6, 2026, and the fix shipped on November 9.
Source: Google, “Chrome Releases” (2026-11-09); The Hacker News (2026-11-10)
The one-minute check (desktop)
- From Chrome’s menu (the ”︙” icon, top right), choose “Help” → “About Google Chrome”
- Your current version number appears, and the update check starts on its own
- If a “Relaunch” button appears, press it. Your tabs come back afterwards (incognito windows do not)
You are patched for this flaw at version 157.0.8103.50 or later on Linux, and 157.0.8103.50/.51 or later on Windows and macOS. One warning: the first Chrome 157 builds (157.0.8103.38 and .39, from November 3) do not include this fix. Do not stop at “157” — read the number to the end.
Source: Google, “Chrome Releases” (2026-11-09)
Phones and other browsers
- Android Chrome: open Chrome in the Play Store and tap “Update” if offered. You can see the version under Settings → About Chrome. The fix is in 157.0.8103.50 and later
- Chrome on iPhone and iPad uses a different engine inside, and is not listed as affected by this flaw. Updating from the App Store when offered is still sensible
- Browsers built on the same base as Chrome, such as Microsoft Edge, are affected too. Edge received the fix in version 157.0.4341.46, confirmed on November 20. In Edge, check your version at edge://settings/help
Source: CISA, Known Exploited Vulnerabilities Catalog (2026-11-10); Microsoft security update information (checked 2026-11-20)
The November 24 date is a measure of urgency
U.S. federal agencies were told to finish dealing with this flaw by November 24. That deadline binds U.S. government offices, not us. But “already exploited, with a deadline set for agencies” is a useful measure of how urgent this is. It is not the kind of thing to leave for later.
Source: CISA, Known Exploited Vulnerabilities Catalog (added 2026-11-10)
In short — the browser is your front door
The browser is the front door to the online world: shopping, banking, and work nearly all pass through it. When a flaw is found in the door’s lock, you swap the lock. This is the same thing.
There is only one action: after reading this, open the “About Google Chrome” screen once, and if the Relaunch button is there, press it. That is all.
Note: each flaw gets a worldwide ID number, called a CVE. This one is CVE-2026-125350. Adding that number when you search or ask someone makes everything faster.
Entrance (other languages)