Apple’s platform-security guide on quantum-secure cryptography, in the edition whose published date is 28 January 2026, extends the story beyond iMessage. After restating Harvest Now, Decrypt Later and Apple’s hybrid philosophy — combine classical and post-quantum algorithms so an update cannot be weaker than the field-tested classical code — the page lists deployments that it says shipped with iOS 26, iPadOS 26, macOS 26, tvOS 26, and watchOS 26. What was announced, in Apple’s words, is as follows. TLS and HTTPS: quantum-secure encryption in the URLSession and Network framework APIs, enabled by default for system services and apps that use those APIs, because browsing and email are high-volume harvest targets. VPN: quantum-secure encryption in the native VPN client and in developer IKEv2 APIs, including a path for third-party VPNs to turn it on. SSH on Mac: a quantum-secure key exchange in macOS 26. Apple Watch: additional ML-KEM key exchanges between iPhone and Watch in iOS 26 and watchOS 26. Developer APIs: CryptoKit adds ML-KEM 768 and ML-KEM 1024 for encryption and ML-DSA-65 and ML-DSA-87 for quantum-secure authentication, with an explicit warning that algorithms must be used inside well-analysed protocols. The same page points back to the 21 February 2024 PQ3 blog for messaging. Together the two documents are Apple’s official map of where post-quantum cryptography is supposed to appear in its OS family. The 2026 guide’s important caveat is printed as “Important: Systems support quantum encryption only when they connect to supporting servers.” A Mac on macOS 26 speaking TLS to a server that does not offer a hybrid group will not magically become quantum-safe. Third-party VPN apps that do not adopt the IKEv2 APIs will not inherit the native client’s behaviour. Apps that implement TLS with non-Apple stacks are outside URLSession’s default. What has not been confirmed on these pages includes a regulatory deadline, a deprecation date for classical-only TLS 1.2 to public websites, performance numbers, or a claim that every iCloud service endpoint supports ML-KEM. CryptoKit exposing ML-DSA does not mean iMessage authentication has moved to ML-DSA; the 2024 PQ3 post said sender authentication stayed on elliptic-curve signatures. Developers who sprinkle ML-KEM into a home-grown chat protocol have not obtained PQ3’s rekeying properties. This is a roadmap-watch item because it is Apple describing OS-level capabilities tied to a named release train, not a rumour about future iPhones. It is not a promise that Bangladesh ISPs, banks, or government sites will offer hybrid TLS. Those servers are independent. What this means in practice Users who can install the iOS 26 / macOS 26 train get hybrid TLS for apps that use Apple’s networking APIs, and Watch-to-iPhone links that Apple says include ML-KEM. They still need updated servers on the other end. App developers in Dhaka or elsewhere should read CryptoKit’s parameter notes and not treat ML-KEM as a drop-in for Signal. VPN administrators should ask vendors whether they call Apple’s IKEv2 post-quantum APIs. Cyber71 cannot enable ML-KEM on a bank’s CDN or certify a VPN tunnel. What is still unclear Apple’s public guide does not list which first-party hosts already negotiate hybrid TLS, how fallback is signalled to users, or whether enterprise MDM can disable the new groups. Interoperability with non-Apple post-quantum TLS drafts may lag. The naming “iOS 26” is Apple’s; this briefing does not reinterpret it as a calendar year of consumer availability in every market. Apple’s hybrid stance also means a software update is not a reason to turn off classical algorithm monitoring. The company wrote that it keeps field-tested elliptic-curve implementations because they have been hardened against side-channel key recovery that exploits CPU signals during algorithm execution. Administrators who only look at “PQC on” checkboxes can miss a network path that still uses a non-Apple TLS library inside a browser extension, a Java mail client, or a government VPN that has not enabled IKEv2 post-quantum transforms. The 28 January 2026 guide is a catalogue of Apple-controlled surfaces, not of the whole internet path a Bangladesh user traverses to reach Gmail or a local bank. Users who cannot yet install the iOS 26 train still have PQ3 on iMessage from the 17.4-era release, which is a different protocol and a different threat (recorded iMessage ciphertext) than hybrid TLS to websites. Mixing those two stories leads to false comfort: an updated Messages app does not encrypt an HTTPS session that never offered ML-KEM.

Sources

  1. Apple Platform Security — Quantum-secure cryptography in Apple operating systems2026-09-24
  2. Apple Security Research — iMessage with PQ3: The new state of the art in quantum-secure messaging at scale2026-09-24

Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.

All research

Need help with a security issue?

Describe the situation and we will open a private case for follow-up.

Get Security Help