Yes. Google Chrome has supported hybrid post-quantum TLS since version 124 (April 2024), using X25519Kyber768 for key exchange.
Key Takeaway: Chrome is considered quantum safe. Uses ML-KEM-768 (FIPS 203) in hybrid mode with X25519.
Google Chrome is quantum safe for TLS connections as of version 124. Chrome uses X25519Kyber768Draft00, a hybrid key exchange that combines classical X25519 with ML-KEM-768 (Kyber). This protects all HTTPS connections to servers that support the hybrid key exchange. Google has deployed this across Chrome on all platforms. The hybrid approach ensures that even if ML-KEM is later found to have weaknesses, the classical X25519 component maintains security.
| Full Name | Google Chrome Browser |
| Category | communication |
| Quantum Vulnerability | TLS connections to servers that do not support hybrid PQC still use classical-only key exchange. |
| NIST Status | Uses ML-KEM-768 (FIPS 203) in hybrid mode with X25519. |
| Deprecation Timeline | Already quantum safe for supported connections |
| Replaced By | N/A — Chrome has already deployed hybrid PQC for TLS |
Ensure Chrome is updated to version 124 or later. Verify server-side PQC support using QScout.
Chrome is quantum safe, but your cryptographic posture is only as strong as its weakest link. QScout maps your entire cryptographic inventory in 7 days.