What Google fixed
Google's November bulletin came out on November 2 and was updated on Friday. Counted together, it covers 216 bugs, 23 of them rated critical. They come in two layers, and the layer your phone gets matters:
- The November 1 patch level covers Android itself: 8 critical and 110 high. This is the part every Android phone needs, whatever chip is inside.
- The November 5 patch level adds the kernel and the chip makers' code (Qualcomm, MediaTek, Arm and others): 15 more critical, 82 high. Eight of those critical ones are in MediaTek modems.
The worst bug is CVE-2026-58868, a remote code execution flaw in the Android Framework. Google says it needs no extra permissions and no tap from you, and it reaches back to Android 14. Two more critical code execution bugs are in the System component. Google hasn't marked any of them as being used in attacks. (Android Security Bulletin, SecurityWeek)
You may have read that these flaws can be triggered by a booby-trapped MMS or a network packet. Neither Google nor the security outlets that covered the bulletin say that. What they say is that it needs no interaction, which is bad enough.
The "SMS of Death"
The bug most likely to affect a normal person is a different one. CVE-2026-58882, which its finder calls the "SMS of Death," is a critical flaw where a single malformed WAP Push message (a type of text message carriers use for settings) crashes the phone app. If you're on a call, the call drops, and that includes an emergency call. It doesn't let anyone into your phone, but being able to knock someone off a 911 call with one text is serious.
The researcher, Mark Blaszczyk, says he reported it to Google on May 5 and published the details on October 29, so there is public proof-of-concept code. Nobody has reported it being used against real people. The fix is in the November 1 patch level, for Android 14 through 17. (CyberInsider)

Pixel: late this month
Pixels usually get the update within a day or a week of Google's bulletin. As of Saturday, Google's Pixel bulletin still listed October as the latest, with no November build or device list. Android Authority found code references suggesting Google might ship the next quarterly Android 17 update to Pixels early instead of a plain security build; Google hasn't said so, so treat that as a guess. (Pixel Update Bulletin, AndroidPure, Android Authority)
If you still have a Pixel 6 or 6 Pro, October's update was its last scheduled one, as I wrote last month. This is the first month where bugs this serious stay open on those phones for good.
Galaxy: still waiting, and the S25 update isn't it
As of Saturday I couldn't find a single Galaxy confirmed to have the November patch, with a model, region and build number. SamMobile expects it "in the coming days," and SammyGuru says the rollout hasn't started. One site reported it was already live on the S26 and the foldables, with no builds or regions to back that up, and every Samsung-focused outlet I checked says otherwise. New US S26 builds this week stayed on the October patch. (SamMobile, SammyGuru)
Meanwhile, the Galaxy S25, S25+, S25 Ultra and S25 FE started getting an update this week, between about 460 MB and 710 MB depending on the model. It's a stability update, and it keeps the October patch. Install it, but don't assume you're covered for November afterwards. (Android Headlines, SamMobile)
One thing I left out on Friday: Samsung's November patch also includes four fixes for its own Exynos chips and modems, rated high. Samsung hasn't described what they fix. On the One UI 9 side, the Galaxy A06 5G, A07 5G, A15 and XCover 7 started getting stable One UI 9 in parts of Asia since Wednesday, and the Galaxy A04e and M04 are now out of support. (Samsung Mobile Security, SammyGuru)
How to check your own phone
- Pixel: Settings, Security and privacy, System and updates. Look at "Security update." November means a date of November 1 or November 5, 2026.
- Galaxy: Settings, About phone, Software information, "Android security patch level." You want November 1, 2026 or later.
- Any phone: if it still says October after an update, that update wasn't the security patch. Check again in a few days.
What I'd do
Nothing dramatic. None of these bugs is known to be in use, and you can't install a patch your phone maker hasn't sent. When the November update shows up, install it that day rather than letting it sit. If your phone is past its support window, like the Pixel 6 or the Galaxy A04e, this is a good month to start planning the replacement, because the fixes aren't coming.
If you missed it, Friday's post covers Samsung's own November fixes and One UI 9 on the Galaxy A phones.
Verified November 7, 2026, from Google's Android bulletin (version 1.1), the Pixel Update Bulletin, Samsung's bulletin, SecurityWeek, CyberInsider, Android Headlines, SamMobile and SammyGuru. Some coverage said the S25 update came from carriers and that the bugs spread through MMS; neither holds up. Written Saturday for Monday evening, so the Pixel and Galaxy updates may have started by the time you read this.
Comments
Be kind and stay on topic.
No comments yet. Be the first.