Security Digest · Nov 2, 2026 · Vulnerability · Mobile
Android November Patch: Zero-Click RCE CVE-2026-58868
Android 14-17 devices below patch level 2026-11-01 are open to a zero-click RCE. No exploitation known yet. Roll out the November update this week.
Our verdict
Patch this week
Google rates this a critical remote code execution bug that needs no tap, but no exploitation is reported and the attack path is undisclosed: move phones to patch level 2026-11-01 this week, on the normal fast track rather than as an emergency.
Who must act: Anyone managing Android 14, 15, 16, 16-qpr2 or 17 devices that reach company data, especially phones used by executives, administrators and on-call staff.
Who can relax: Devices already reporting security patch level 2026-11-01 or later; there is no sign of attacks so far, so this does not call for out-of-hours work.
- Affected
- Android 14, 15, 16, 16-qpr2 and 17 below security patch level 2026-11-01 (CVE-2026-58868, CVE-2026-58882)
Android 12 and 13 are not listed; Google's records do not say whether they contain the flaws - Fixed in
- Android security patch level 2026-11-01 or later
Samsung SMR-NOV-2026 (lists both CVEs)
Patch level 2026-11-05 or later closes every issue in the November bulletin - CVSS
- 9.8 (v3.1, CISA-ADP)
- EPSS
- 7.1% (percentile 94)
- CISA KEV
- Not listed
- Exploitation
- No known exploitation
- Severity
- Critical
What to do
- Pull a device report from your MDM and flag every Android 14-17 device below security patch level 2026-11-01.
- Push the manufacturer's November update and set a deadline of about a week for the flagged devices.
- Prioritize phones used by administrators, executives and on-call staff, and phones that receive one-time codes.
- Confirm the new patch level in the device report after installation; a queued update does not count.
- Restrict company access from devices that cannot reach 2026-11-01, including Android 13 and older, or plan to replace them.
- Track 2026-11-05 as a separate target to close the kernel and chipset issues in the same bulletin.
How to check if you are affected or compromised
- Run adb shell getprop ro.build.version.security_patch, or read Settings > About phone > Android version, to get the patch level.
- No indicators of compromise have been published for CVE-2026-58868 as of Nov 8, 2026; treat a missing or stale patch report as unresolved.
- For the SMS crash bug, look for repeated com.android.phone crashes and dropped calls with adb logcat -b crash -d.
What happened#
On November 2, 2026, Google published the Android Security Bulletin for November, with more than 200 fixes and 23 issues rated Critical. Google calls the worst of them a critical Framework vulnerability that "could lead to remote code execution with no additional execution privileges needed." The bulletin adds: "User interaction is not needed for exploitation."
That bug is CVE-2026-58868. The CVE record describes a possible out-of-bounds write from a heap buffer overflow in onOutputReceived in FrameDecoder.cpp. CISA's enrichment of the record scores it 9.8 on CVSS 3.1. CISA's SSVC assessment lists exploitation as "none," automatable as "yes" and technical impact as "total."
A second Critical bug drew attention for a different reason. CVE-2026-58882 is a remote denial of service in decodeWapPdu of WapPushOverSms.java, caused by an integer overflow that leads to an out-of-bounds read. CISA scores it 7.5, while Google's bulletin rates it Critical.
On October 29 a researcher publishing as Mark B released the "SMS of Death" write-up, with a public proof of concept, for a crash in the same function. A malformed WAP Push message crashes com.android.phone and drops active calls, including emergency calls. The researcher describes the attack as silent and repeatable on redelivery and boot.
The link between the two is not confirmed. As The Hacker News notes, neither Google's bulletin nor the CVE record says they are the same bug. The researcher also says a fix shipped in the October update, a month before this CVE appeared in a bulletin.
Who is affected#
Both CVE records list Android 14, 15, 16, 16-qpr2 and 17. Both fixes are in the 2026-11-01 patch level section, so a device at that level or later has them. The fix for CVE-2026-58868 arrives through the manufacturer's update, not through a Google Play system update, and carriers and manufacturers ship on their own schedules. Samsung's SMR-NOV-2026 lists both CVEs.
Android 12 and 13 are not in the affected lists, and Google's records do not say whether those versions contain the flaws. For the WAP Push crash, the researcher says Android 12 and 13 run the vulnerable code and get no fix. Treat those devices as unprotected.
Do you really need to act?#
Yes, this week, but without panic. A remote, no-interaction code execution bug on Android is rare and serious. Three things keep it out of the drop-everything category as of November 8:
- The bulletin makes no statement about exploitation, and CISA's assessment of the record lists none.
- CVE-2026-58868 is not in the CISA KEV catalog.
- Google has not said how an attacker reaches the vulnerable code, so "zero-click" may depend on conditions nobody outside Google can yet assess.
Google's severity rating also assumes platform and service protections are turned off or bypassed, which is standard for its bulletins. The clock matters anyway. Google says it publishes source patches to AOSP within 48 hours of the bulletin, so researchers can already compare the code, and a bug this valuable will get that attention. Phones also tend to hold one-time codes and signed-in work accounts, so a single compromised device can reach a lot.
The SMS crash is lower risk for data but matters for anyone who depends on a phone being reachable. It needs only a phone number, and a public proof of concept exists.
What to do now#
- Export model, Android version, patch level and last check-in from your MDM, and flag Android 14-17 devices below 2026-11-01. Treat devices with missing or stale data as unresolved.
- Push the manufacturer's November update and give flagged devices about a week.
- Start with administrators, executives, on-call staff and phones that receive one-time codes.
- Check a single device with
adb shell getprop ro.build.version.security_patch, or in Settings > About phone > Android version. - Limit company access from devices that cannot reach 2026-11-01, and plan to replace them.
- Set 2026-11-05 as a separate target. That level adds the kernel, Arm, Imagination, MediaTek, Unisoc and Qualcomm fixes from the same bulletin.
How to tell if you were hit#
For CVE-2026-58868, no indicators of compromise have been published as of November 8, 2026, and installing the update will not reveal earlier activity. Investigate only if you have other reasons for concern, such as unexplained account access from a managed phone.
For the WAP Push crash, look for repeated com.android.phone failures and calls dropping for no reason. adb logcat -b crash -d shows recent crashes. The researcher's write-up names NegativeArraySizeException as the exception to look for, and describes an ADB recovery for Android 12 devices stuck in a boot loop.
Timeline#
- — The researcher reports the WAP Push crash to Google.
- — "SMS of Death" write-up and proof of concept are published.
- — Google publishes the November bulletin and CVE records for CVE-2026-58868 and CVE-2026-58882.
- — Samsung publishes SMR-NOV-2026. CISA's assessment of CVE-2026-58868 lists no exploitation.
- — Google updates the bulletin's issues list to version 1.1.
Vulnerability records
- CVE-2026-58868 · In onOutputReceived of FrameDecoder.cpp, there is a possible out-of-bounds write due to a heap buffer overflow.
- CVE-2026-58882 · In decodeWapPdu of WapPushOverSms.java, there is a possible out of bounds read due to an integer overflow.
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- Android Open Source Project — Android Security Bulletin, November 2026 source.android.com
- CVE.org — CVE-2026-58868 record cve.org
- CVE.org — CVE-2026-58882 record cve.org
- Samsung Mobile Security — Security Updates (SMR-NOV-2026) security.samsungmobile.com
- Mark B — SMS of Death write-up smsofdeath.com
- Hive Security — Android's November patch: verify the fix for CVE-2026-58868 hivesecurity.gitlab.io