Components

Browse post-quantum support by protocol and application, with versions, defaults and requirements.

Secure TLS connections

Check hybrid key exchange and handshake signatures in browsers, runtimes and TLS implementations.

Browsers

4

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 131

Requirements:

Switched from the draft X25519Kyber768Draft00 group to standard X25519MLKEM768 in 131 and removed the legacy draft group.

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 131.0.2903.48

Requirements:

Switched to standard X25519MLKEM768 in 131 and removed the draft Kyber group; Edge 147 removed the enterprise policy toggle, keeping hybrid key exchange always enabled.

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 132

Requirements:

Enabled by default on desktop starting in 132 (manageable via the PostQuantumKeyAgreementEnabled enterprise policy); ESR and mobile releases follow separate rollout schedules.

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 26 / OS 26

Requirements:

TLS capabilities depend on the OS; upgrading Safari on an older macOS still requires checking OS support.

Application runtimes

3

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 1.24

Requirements:

Enabled by default when tls.Config.CurvePreferences is empty, or add tls.X25519MLKEM768 if a custom list is set; the 1.24 standard library does not yet include ML-DSA or SLH-DSA.

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 27

Requirements:

JDK 24 provides JCA algorithm APIs for ML-KEM and ML-DSA only; TLS 1.3 hybrid key exchange in SunJSSE requires JDK 27.

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 24.5.0

Requirements:

Official 24.5.0+ binaries bundle OpenSSL 3.5, whereas distro builds dynamically linked against system OpenSSL 3.0 lack post-quantum support; algorithm APIs arrive across 24.6–24.8.

TLS implementations & crypto libraries

8

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 3.5.0

TLS 1.3 · ML-KEM-only key exchange

SupportedSince 3.5.0

TLS 1.3 · Hybrid SM2-MLKEM key exchange

SupportedSince 4.0.0

Requirements:

Built into the default provider in 3.5+ without extra plugins; many Linux LTS distributions still ship 3.0.x, so services dynamically linking the system library must check the loaded version.

rustls

  • Rust

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 0.23.27

Requirements:

Requires the default aws-lc-rs backend and prefer-post-quantum feature; switching to the ring backend or disabling default features turns off post-quantum key exchange.

s2n-tls

  • C / C++

TLS 1.3 · Hybrid key exchange

SupportedSince 1.5.6

TLS 1.3 · Signatures

SupportedSince 1.5.19

Requirements:

Must be linked against AWS-LC (post-quantum features are unavailable with OpenSSL) and configured with a PQ security policy such as default_pq; ML-DSA authentication requires AWS-LC 1.50.0+.

BoringSSL

  • C / C++

TLS 1.3 · Hybrid key exchange

SupportedSince 7fb4d3da5082

Requirements:

Tracks rolling Git commits rather than numbered releases; TLS hybrid groups are not enabled by default and must be configured by the host application.

GnuTLS

  • C / C++

TLS 1.3 · Hybrid key exchange

ExperimentalSince 3.8.8

TLS 1.3 · Signatures

ExperimentalSince 3.8.10

Requirements:

Must be built with the external leancrypto (3.8.10+) or liboqs backend and enabled at runtime through the priority string.

NSS

  • C / C++

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 3.118

Requirements:

Supports X25519MLKEM768 when explicitly enabled in 3.105+ and enables it by default in libssl starting in 3.118; Firefox manages its own rollout and policies.

TLS 1.3 · Hybrid key exchange

SupportedSince 5.8.0

Requirements:

Disabled in default builds; enable the ML-KEM, ML-DSA and hybrid-group compile-time macros and configure the allowed TLS groups.

Botan

  • C / C++

TLS 1.3 · Hybrid key exchange

Enabled by defaultSince 3.7.0

TLS 1.3 · ML-KEM-only key exchange

SupportedSince 3.7.0

Requirements:

Enabled in the default TLS::Policy since 3.7.0; custom policies overriding key_exchange_groups() or minimized builds must explicitly include the ML-KEM modules.