iOS 26.5 and iPadOS 26.5 release adds end-to-end encrypted RCS messaging

Apple’s latest point release is really about messaging security. iOS 26.5, released on May 11, adds end-to-end encrypted RCS chats in Messages — but only on supported carriers, and only as that support rolls out. iPadOS 26.5 arrived the same day, though the headline feature is mostly an iPhone story. (developer.apple.com) The bigger point is simple: green-bubble texting just got more capable, and in some cases, actually private. (support.apple.com) ### What actually changed in 26.5? On iPhone, Apple says iOS 26.5 introduces end-to-end encrypted RCS messaging in beta, plus a downloadable Pride Luminance wallpaper, Maps suggestions for trending nearby places, bug fixes, and security updates. iPadOS 26.5 gets the wallpaper, Maps suggestions, fixes, and security updates — but Apple’s update notes do not list encrypted RCS as an iPadOS feature. (support.apple.com) ### Why is encrypted RCS a big deal? RCS is the modern replacement for old-school SMS and MMS. It brings typing indicators, read receipts, higher-resolution media, and better group messaging, but historically it has not always had the same privacy guarantees people expect from iMessage. (developer.apple.com) With 26.5, Apple is finally enabling end-to-end encryption for RCS conversations in Messages, which means the content can be protected in transit between devices when the whole chain supports it. ### So are all green bubbles encrypted now? No — and that’s the part people will miss. (support.apple.com) Apple says encrypted RCS depends on your carrier supporting it, your contact’s carrier supporting it, and the conversation showing an “Encrypted” label with a lock icon at the top. If that indicator is missing, the messages are not protected from third-party access while traveling between devices. Basically, 26.5 adds the capability, not universal coverage on day one. ### Why does the carrier matter so much? Because RCS is still a carrier-provided service. Apple’s support docs spell out that your phone exchanges identifiers with your carrier and partners to set up the connection, and availability varies by region and carrier. (support.apple.com) That is very different from iMessage, where Apple controls the whole stack. So the user experience here depends on telecom plumbing Apple doesn’t fully own. ### Where did this encryption standard come from? This did not appear out of nowhere. In March 2025, the GSMA published RCS Universal Profile 3.0, which added the requirements and user experience for end-to-end encryption of RCS messages, files, and other user content. (support.apple.com) Last month, the GSMA said cross-platform encryption testing between Android and iOS devices was underway, which helps explain why Apple could now flip this on in beta. ### Is this also a security update? Yes — and that matters even if you never use RCS. (support.apple.com) Apple published a dedicated security advisory for iOS 26.5 and iPadOS 26.5 on May 11 covering vulnerabilities across system components. The public advisory is long, which is usually a sign this is not a cosmetic release. For most people, that alone is reason enough to install it. ### What should developers and IT teams take from this? Two things. First, messaging behavior on iPhone is changing again, especially for apps and workflows that assume green-bubble chats are unencrypted fallback channels. (gsma.com) Second, 26.5 is part feature update, part security baseline, so teams that manage fleets of devices should treat it like an important maintenance release, not a nice-to-have. That’s an inference from Apple’s release notes and security bulletin — but it’s a pretty straightforward one. ### Bottom line? iOS 26.5 does not magically make every iPhone-to-Android text private. (support.apple.com) But it does close one of the biggest remaining gaps in modern messaging — and that is a meaningful shift. If your carrier supports it, green bubbles just got a lot less stuck in 2012. (support.apple.com 1) (support.apple.com 2)