A bug in Google Messages has been reviving old texts and attaching them to new conversations, sending private messages meant for one person into an entirely different contact’s thread. The issue has surfaced across both RCS and SMS conversations on Android, and it carries an obvious privacy problem: a message written for a spouse, a coworker, or a doctor’s office can resurface days or weeks later inside a conversation with someone who was never supposed to see it.
What the Bug Actually Does
The malfunction happens when a person composes a new message to one contact and Google Messages, rather than sending only that message, also pulls in an old text originally sent to a completely different contact and delivers both together. The old message is not a duplicate of anything recent; it can be pulled from well back in a person’s message history, meaning the content that resurfaces is often something the sender had long since forgotten about. Because the bug spans both RCS, the newer messaging standard Google has pushed as a replacement for traditional SMS, and plain SMS itself, it is not limited to a single type of conversation or a specific phone model.
The Privacy Risk Hiding in Old Conversations
The concern is not just embarrassment over an out-of-context message. Old text threads frequently contain information nobody intends to keep resending: one-time verification codes, addresses, financial details, or messages exchanged during a sensitive personal situation. When those resurface attached to an unrelated new message, the recipient gets a window into a conversation that has nothing to do with them, and the original sender has no warning before it happens. For anyone using text messages to receive two-factor authentication codes, an old code resurfacing in a new thread is a particularly sharp example of how a bug like this moves beyond inconvenience into a real security exposure.
The randomness of which old message resurfaces, and which new contact receives it, is part of what has made the bug hard to predict or avoid. Affected users have reported the issue appearing without any obvious trigger, meaning there is no specific action, like sending a particular kind of message or messaging a particular contact, that reliably causes or prevents it. That unpredictability has made the bug difficult for both Google’s engineers to isolate quickly and for affected users to work around in the meantime.
Google’s September 2 Acknowledgment
Google confirmed the problem on September 2, 2026, stating that it was rolling out a fix intended to reach everyone over the following weeks. The company advised users to keep Google Messages updated to the most recent version, since the rollout is being delivered as a server-side and app-level fix rather than something users can trigger manually. Google’s phrasing suggested the rollout would be gradual rather than immediate, arriving in stages across the Android user base instead of landing everywhere at once.
Google did not publish a detailed technical explanation of what caused old messages to resurface in the first place, limiting its public comments to confirming the bug’s existence and describing the timeline for a fix. That relatively brief acknowledgment left the specifics of how the error occurs, and how widespread it ultimately was before the fix began rolling out, largely undisclosed.
Why Reports Kept Coming After the Fix Began
Despite that acknowledgment, new reports of the bug were still surfacing close to a week after Google’s statement, an indication that the gradual rollout had not yet reached every affected device. That gap between an official fix being announced and the bug still occurring in the wild is common with staged software updates, but it leaves an uncertain stretch of time during which some users remain exposed while others have already received the correction. Some builds distributed through Google’s Play beta channel in early September appeared to include changes related to the issue, suggesting that people enrolled in the beta program may see the fix reach their devices sooner than those on the standard release track.
What to Do Until the Fix Reaches Every Device
Keeping the Google Messages app updated to its latest version is the most direct step available, since Google has tied the fix to that rollout rather than to any setting a user can toggle. People who rely on text messages for two-factor authentication codes may want to pay closer attention to which messages appear in which threads over the coming weeks, since a resurfaced old code mixed in with a legitimate new one could otherwise go unnoticed. Anyone enrolled in Android’s beta testing programs has a reasonable chance of receiving the corrected build earlier than the general release schedule would otherwise provide, which may be worth considering for users especially concerned about the exposure in the meantime.
For anyone who receives an old, out-of-place message from a contact using Google Messages, the safest assumption is that the sender did not intend to share it and the content should be treated as accidental rather than a genuine new communication. Flagging the mix-up to the sender directly, rather than acting on whatever information appeared in the resurfaced text, is a reasonable precaution while Google continues rolling the fix out across the Android user base over the coming weeks.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- More than 60,000 people flee the Spokane area as complex fires overrun 600 structures
- 11 engines built to run well past 200,000 miles
- Card skimmers hidden on gas pumps and ATMs are draining accounts, and here’s the tell
- The FBI says hackers are hijacking outdated home routers, and it named the models to check
