Apple addresses security vulnerability that allowed the FBI to retrieve messages from notification history on the iPhone.

      Apple's notification glitch didn't only impact disappearing messages; it cached the content of any notification for up to a month, transforming a normal iOS function into an unintentional issue.

      When you delete a message, it should be removed, right? Clearly, the iPhone's notification database didn't get the memo.

      On April 22, 2026, Apple issued a security update for iPhones and iPads, silently fixing a flaw that permitted law enforcement, including the FBI, to retrieve messages users believed they had erased.

      How did deleted messages become retrievable?

      The explanation lies in how iOS managed notification caching. When a message was received, iOS generated a notification, archiving the message content in a locally stored database (which could persist for up to a month).

      Even if the original message was erased within the app, it remained in this database. While one could label this as a loophole or a flaw, it also impacted disappearing messages intended for users concerned about privacy.

      A report from TechCrunch (referencing 404 Media) indicated that FBI agents could extract deleted Signal messages from an iPhone using forensic methods, as those messages appeared in notifications and were saved in the notification database. They remained accessible long after being deleted from the app itself.

      In principle, the problem could have also impacted messages from other applications since they also appear as notifications on an iPhone.

      Who called Apple out on this?

      Meredith Whittaker, the president of Signal, vocally criticized Apple for the issue, insisting that notifications for deleted messages should not linger in any operating system's database.

      Apple's security notice has acknowledged that “notifications marked for deletion could be unexpectedly retained on the device,” describing it as a significant issue rather than simply an error.

      Currently, the security fix is available for devices operating on the most recent iOS 26 and has been backported to users still on iOS 18. However, Apple has not clarified why this issue, originating from operating system-level caching behavior, existed initially.