Apple CryptoKit and Network framework

Apple's Swift cryptography API and the system TLS stack on iOS and macOS.

Ready

PQC is supported in a stable release and enabled by default where it applies (for example, hybrid key exchange on by default).

Ecosystem
OS / platform
Homepage
developer.apple.com
Last verified

What to do

ML-KEM, ML-DSA and hybrid TLS key exchange: Apple CryptoKit and Network framework 26.0 or later. On by default: hybrid TLS key exchange.

Algorithm support

AlgorithmSupportSinceOn by defaultExperimentalNotes
ML-KEM
FIPS 203
Supported[1]26.0?No
ML-DSA
FIPS 204
Supported[2]26.0?No
Hybrid TLS
e.g. X25519MLKEM768
Supported[3]26.0YesNo

Roadmap

No public roadmap recorded.

FIPS validation (PQC)

Unknown.

Evidence

  1. CryptoKit MLKEM768 (iOS 26.0, macOS 26.0 and later) · docs · retrieved 2026-11-13
    The Module-Lattice key encapsulation mechanism (KEM).
  2. CryptoKit MLDSA65 (iOS 26.0, macOS 26.0 and later) · docs · retrieved 2026-11-13
    The MLDSA65 Digital Signature Algorithm
  3. Prepare your network for quantum-secure encryption in TLS - Apple Support · docs · retrieved 2026-11-14
    In iOS 26, iPadOS 26, macOS Tahoe 26, and visionOS 26, TLS-protected connections will automatically advertise support for hybrid, quantum-secure key exchange in TLS 1.3.

Out of date? Ask us to re-check Apple CryptoKit and Network framework against its latest releases, or suggest a correction or edit the data file on GitHub.

Machine-readable: /api/libraries/apple-cryptokit.json · Data from PQC Deps, CC BY 4.0.