Skip to main content

Morning Overview

Samsung’s November Galaxy update patches a critical flaw hackers could exploit remotely

Galaxy phone owners who see a software update notification this month are being offered fixes for a long list of security flaws. One of them sits in the core of Android, and Google rates it as critical because it could let an attacker run code on a phone remotely, without the owner tapping anything.

Read next on Morning Overview: Melting permafrost is setting off a newly identified kind of catastrophic landslide, scientists say

Samsung published its November 2026 security bulletin on Nov. 3. It bundles Google’s Android patches with 24 Samsung-specific security items and four high-severity flaws in Samsung’s semiconductor components. Neither company says the critical bug is being exploited, but that is the kind of flaw attackers prize.

A critical remote code execution flaw in Android’s Framework

The most serious issue sits in Android’s Framework layer, the system software that apps and the operating system rely on. Google’s November 2026 Android Security Bulletin describes a critical vulnerability there that could allow remote code execution with no additional execution privileges and no user interaction needed. Google’s severity rating assumes that some of Android’s built-in protections are disabled or have been bypassed, which is standard for how it scores flaws, but a bug that needs no tap or click is the most worrying category for phone users.

Google’s bulletin is dated Nov. 1 and comes in two patch levels. A phone at the Nov. 1, 2026, security patch level has the fixes for that level and earlier months; a phone at Nov. 5 has every applicable fix from both November levels. A related eSecurity Planet report on Google’s bulletin counted 216 Android vulnerabilities addressed across the month, including critical remote code execution flaws.

Remote code execution means an attacker can make the phone run instructions of the attacker’s choosing from a distance, for example through a crafted file, message or network traffic, rather than needing the device in hand. Paired with a second flaw that raises privileges, a remote bug can become the first step toward full control of a phone, which is why vendors and security agencies rank this category above almost everything else. The absence of a required tap removes the most common safeguard, a cautious user who simply does not open the suspicious link.

24 Samsung items and four semiconductor flaws

On top of Google’s fixes, Samsung’s security bulletin lists 24 items specific to Galaxy software and four high-severity semiconductor vulnerabilities, eSecurity Planet reported. Among the Samsung-specific bugs are a high-severity flaw in the bootloader, CVE-2026-21155, that could let an attacker with physical access write data outside an intended memory boundary; a high-severity camera library bug, CVE-2026-21152, that could let a local attacker run code if a user interacts; and a stack-based buffer overflow in a Samsung software library, CVE-2026-21153, rated high. A moderate flaw in Samsung Messages, CVE-2026-21148, could expose sensitive information.

Several moderate issues in the Contacts app could have let local attackers start calls without the permissions normally required. Samsung fixed them by removing unused code or strengthening access controls.

The bootloader flaw is a reminder that not every bug is remote. Because it requires physical access, it matters most for a phone that is lost or stolen, where an attacker has time to work on the device directly. The camera and software library bugs fall in between: they need an attacker to already have some foothold on the phone, often through a malicious app, before they can be used.

No active exploitation, but Pwn2Own showed the S26 can fall

Neither Google’s nor Samsung’s bulletin establishes that attackers are actively exploiting these November vulnerabilities, according to eSecurity Planet. Galaxy phones have shown they are not immune, though: in October, researchers exploited the Galaxy S26 multiple times during the Pwn2Own hacking competition, a separate set of flaws from the November bulletin. Pwn2Own findings are reported privately to the vendor and typically patched in later updates.

Which fixes a given phone needs depends on its model, hardware and software version. Several November patches apply to Android 14, 15, 16 or 17, and exposure varies with the device’s chipset and previously installed updates.

Rollout timing for Galaxy phones

Samsung calls the package SMR Nov-2026 Release 1, and availability varies by model, carrier and region. Some patches supplied by chipset vendors may arrive in later packages, so two owners of the same phone in different countries can receive fixes at different times. Samsung’s security update scope page lists which devices receive monthly, quarterly or less frequent updates; older models drop to slower schedules and eventually stop receiving patches.

On supported devices, the installed security level appears in the phone’s settings under the software information section, where Samsung shows the Android security patch level and its own security software version. A phone that shows a November 2026 patch level has the critical Framework fix. One that has not updated, or that has aged out of Samsung’s support window, remains exposed to a remote flaw that needs no help from its owner, which makes checking for the update the most useful step a Galaxy user can take this month.

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.


More from Morning Overview

Morning Overview is reader-supported. Some links in our articles are affiliate links, and we may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Full disclosure.