TL;DR — 15 Second Read
- →Apple has patched CVE-2026-28950, a logging flaw in iOS Notification Services that caused notifications marked for deletion — including Signal messages — to be unexpectedly retained in the device's push notification database rather than being permanently erased.
- →The FBI exploited this flaw forensically in a live court case, extracting copies of incoming Signal messages from a defendant's iPhone even after the Signal app had been completely deleted from the device — proving that "deleted" messages were never truly gone from the operating system level.
- →The patch is available in iOS 26.4.2 and iOS 18.7.8 — once installed, Apple confirms that all inadvertently preserved notifications will be automatically deleted and no future notifications will be retained after deletion.
- →Signal itself is not at fault — the flaw exists entirely within Apple's iOS notification infrastructure. However, Signal users can additionally reduce their exposure by disabling message content in notifications, limiting what the OS ever stores in the first place.
Apple has quietly patched one of the most consequential privacy vulnerabilities discovered on iOS in recent years — a logging bug that caused deleted notifications, including Signal messages, to be permanently retained in the device's push notification database. CVE-2026-28950, addressed in iOS 26.4.2 and iOS 18.7.8 released on April 23, 2026, is not a theoretical data security risk. It is a flaw that the U.S. Federal Bureau of Investigation has already used in a live court case to extract copies of encrypted Signal messages from a defendant's iPhone — messages from an app that had been deleted entirely from the device.
The implications extend far beyond this single case. Every iPhone and iPad running an unpatched version of iOS has been silently retaining deleted notification content in a local database — content that is accessible to anyone with physical access to the device and the forensic tools to read it. For cybersecurity professionals, journalists, lawyers, activists, and anyone who uses encrypted messaging with an expectation of genuine privacy, this patch is not optional. It is one of the most important iOS security updates of 2026.
Affected products
- ·iOS and iPadOS — all versions prior to iOS 26.4.2 (for iPhone 11 and later, iPad Pro 3rd gen and later, iPad Air 3rd gen and later, iPad 8th gen and later, iPad mini 5th gen and later) iOS and iPadOS — all versions prior to iOS 18.7.8 (for iPhone XR, XS, XS Max, iPhone 11 through 16e, iPad 7th gen through current, iPad Air 3rd through M3, iPad Pro 11-inch 1st gen through M4, iPad Pro 12.9-inch 3rd through 6th gen, iPad Pro 13-inch M4)
How to Fix
Step-by-step remediation
Installing the iOS update is the complete remediation. Apple has confirmed that iOS 26.4.2 and iOS 18.7.8 address the logging flaw with improved data redaction in the Notification Services component — meaning the OS will no longer write notification content to the persistent database in a way that survives deletion.
Critically, the patch is retroactive. Signal confirmed that once the update is installed, all notifications that were inadvertently preserved will be deleted automatically. Users do not need to manually clear any databases or take additional steps — the OS cleanup happens as part of the update process.
For privacy hardening beyond the patch: the most effective control is preventing sensitive notification content from ever being delivered to the OS in the first place. In Signal, navigate to Profile → Notifications → Show → select "No name or message." With this setting active, Signal sends a generic notification to iOS ("New message") rather than the actual content — meaning the notification database would contain only the alert type, not the message text, even if the logging bug had not been patched.
For enterprise and high-risk deployment scenarios, MDM administrators should push the iOS update immediately as a mandatory policy update, and consider enforcing notification content restrictions for sensitive communication apps across managed device fleets.
What happened
iOS uses a centralized Notification Services system to receive, display, and manage push notifications from all apps installed on the device. When a notification arrives — for example, a Signal message — the OS briefly receives the notification content to display it as an alert on the lock screen or in the notification center. When the user dismisses or deletes the notification, the expectation is that the content is removed from the system.
CVE-2026-28950 reveals that this expectation was false. Due to a logging bug in the Notification Services component, notifications marked for deletion were being unexpectedly retained in the device's push notification database — a SQLite database stored on the local filesystem. This means that even after a user deleted a Signal notification, dismissed it, or deleted Signal entirely, the message content from that notification remained readable in the underlying iOS notification store.
The FBI's forensic team discovered this database during analysis of a defendant's iPhone and was able to extract copies of Signal messages — messages that the Signal app's end-to-end encryption had protected in transit, messages that the user believed were ephemeral, messages from an app that no longer existed on the device. The encryption protected the messages from network interception. It could not protect them from a logging bug in the operating system that was quietly writing copies of the notification content to disk.
Real-World Impact
The FBI court case is the confirmed real-world instance of this vulnerability being used to extract private communications — but the forensic technique is not exclusive to the FBI. Any party with physical access to an unpatched iPhone and access to commercial forensic tools such as Cellebrite or Graykey could potentially access the same notification database. This includes law enforcement agencies worldwide, corporate IT forensics teams, border agents conducting device searches, and any individual with both physical device access and the technical knowledge to read the notification store.
The digital security and information security implications are particularly acute for high-risk users. Journalists who communicate with confidential sources via Signal, lawyers exchanging privileged communications, human rights defenders operating under authoritarian governments, and activists coordinating sensitive activities all rely on the privacy guarantees of encrypted messaging. CVE-2026-28950 demonstrates that those guarantees can be undermined entirely at the operating system level — not through any weakness in Signal's encryption, but through a bug in the infrastructure Apple uses to deliver notifications to the app.
The Electronic Frontier Foundation's response to this disclosure underscores a broader data privacy challenge: for most app notifications, users have no visibility into what metadata is logged, whether notification content is encrypted at rest, or how long it is retained. This vulnerability makes clear that the answer, in iOS's case, was "longer than anyone expected."
🛡️ Prevention Tips
Install iOS 26.4.2 or iOS 18.7.8 immediately — this is the most important action. The patch both fixes the logging flaw going forward and cleans up all previously retained notification data automatically.
Disable message content in Signal notifications as a permanent privacy setting, not just as a response to this specific vulnerability. The principle is sound regardless of patching status: the less content you allow iOS to handle on behalf of your messaging app, the less content can ever be inadvertently retained, logged, or accessed.
Reconsider whether sensitive apps need push notifications at all. The EFF's guidance applies broadly: if an app handles sensitive communications, evaluate whether notifications — which necessarily route content through Apple's infrastructure — are appropriate. Disabling notifications for specific apps entirely is the most complete way to ensure no notification content ever reaches the iOS notification database.
Be aware that device encryption does not protect locally stored notification databases from forensic extraction when the device is unlocked or when forensic tools can bypass the lockscreen. Physical device security — strong passcodes, immediate locking, and never allowing physical access to your device by untrusted parties — remains a critical layer of computer security independent of any software patches.
FAQs
Does this mean Signal's encryption was broken?
No. Signal's end-to-end encryption remains intact and was not compromised by this vulnerability. The flaw is entirely in Apple's iOS Notification Services component, which briefly receives notification content to display alerts on the device. Signal's encryption protects messages in transit between users — it cannot protect against a bug in the operating system that logs the content of displayed notifications to a local database. The two protections operate at different layers.
f I already deleted Signal from my iPhone, are my old messages still in the notification database?
They may have been prior to this patch. The flaw caused notifications to be retained even after the originating app was deleted. However, once you install iOS 26.4.2 or iOS 18.7.8, Apple confirms that all inadvertently retained notification records will be automatically and permanently deleted — including any from apps that are no longer installed. Install the update immediately.
Does this vulnerability affect WhatsApp, Telegram, or other messaging apps?
Yes — the flaw is in iOS's notification infrastructure, not specific to Signal. Any app that delivers message content through iOS push notifications could have had that content retained in the notification database. Signal was the app identified in the FBI court case, but the underlying logging bug affected all apps using iOS Notification Services. This makes the patch important for all iPhone users, not just Signal users.
Read Next
cohere ai · terrarium
CVE-2026-5752: Cohere AI Terrarium Sandbox Flaw Allows Root Code Execution and Container Escape — No Patch Coming
masjesu · xorbot
Masjesu Botnet: The Stealthy DDoS-for-Hire Service Quietly Hijacking IoT Devices Since 2023 — Now Hitting 300 Gbps
cve 2026 34040 · docker
CVE-2026-34040: Docker AuthZ Plugin Bypass Lets Attackers Escape Containers and Gain Full Host Access — AI Agents Can Trigger It Automatically
php webshell · cookie controlled
Microsoft Exposes Cookie-Controlled PHP Web Shells That Resurrect Themselves via Cron — A New Stealthy Linux Persistence Technique
openai · chatgpt