No. Diffie-Hellman key exchange is not quantum safe. Shor's algorithm solves the discrete logarithm problem that DH security depends on.
Key Takeaway: Diffie-Hellman is NOT quantum safe. Replace DH/DHE with ML-KEM (FIPS 203) for key encapsulation. Use hybrid mode during transition.
Diffie-Hellman is NOT quantum safe.
Diffie-Hellman (DH) key exchange, invented in 1976 by Whitfield Diffie and Martin Hellman, was the first published practical method for establishing a shared secret over an insecure channel. Unlike asymmetric encryption (which encrypts data), DH is a key agreement protocol used to derive symmetric keys for subsequent encryption (typically AES).
The protocol operates in a finite field (modular arithmetic): Alice and Bob agree on public parameters (a large prime p and generator g). Alice chooses a secret integer a and computes A = g^a mod p. Bob chooses secret b and computes B = g^b mod p. They exchange A and B publicly. Alice computes s = B^a = (g^b)^a = g^(ab) mod p. Bob computes s = A^b = (g^a)^b = g^(ab) mod p. Both arrive at the same shared secret s = g^(ab) without transmitting a or b.
Common DH groups include: DH Group 14 (2048-bit prime), Group 15 (3072-bit), and Group 16 (4096-bit). Ephemeral Diffie-Hellman (DHE) generates new private keys for each session, providing forward secrecy — even if the server's long-term private key is compromised, past sessions remain secure.
DH security relies on the discrete logarithm problem (DLP): given g, p, and A = g^a mod p, it should be computationally infeasible to recover a. Classically, the best algorithms (Number Field Sieve) require sub-exponential time, making 2048-bit DH secure against classical attacks (estimated centuries to break).
Shor's algorithm solves the discrete logarithm problem in polynomial time, so larger finite-field DH groups do not create post-quantum resistance. Exact fault-tolerant resource requirements depend on the group, circuit, architecture, and error-correction assumptions.
DHE's forward secrecy provides no protection against quantum adversaries who record key exchanges. An adversary capturing DHE handshakes today can store them and decrypt the sessions once quantum computers mature (HNDL attacks).
Inventory Diffie-Hellman use and migrate it through an approved key-establishment profile:
Enterprise VPN infrastructure (site-to-site and remote access VPNs) extensively uses IKEv2 with DH groups 14-20 for key establishment. Corporate networks connecting remote offices, cloud environments, and remote workers are vulnerable to HNDL attacks. A future quantum adversary could decrypt all VPN traffic captured today, exposing intellectual property, customer data, and internal communications.
Financial services use DH in legacy protocols (older TLS 1.2 configurations, proprietary trading protocols, SWIFT network connections). While most modern systems have migrated to ECDHE, legacy DH deployments remain in production due to interoperability requirements with older systems.
CNSA 2.0 requirements apply to NSS and related acquisition or interoperability contexts. The December 2024 FAQ describes staged 2027 acquisition, 2030 phaseout, and 2031 algorithm-use dates unless otherwise noted; it does not establish a universal 2030 mandate for every DH deployment.
Industrial control systems and SCADA networks use VPNs with DH key exchange to connect remote substations, manufacturing plants, and utility infrastructure. These systems have long operational lifetimes (20-30 years) and slow patch cycles, creating extended vulnerability windows.
Set transition dates from observed DH use, capture exposure, data lifetime, applicable policy, supported profiles, interoperability evidence, and rollback readiness.
| Full Name | Diffie-Hellman Key Exchange (DH / DHE) |
| Category | key exchange |
| Quantum Vulnerability | Shor's polynomial-time discrete-log algorithm applies to finite-field DH at every standardized group size; exact attack resources vary. |
| NIST Status | NIST IR 8547 (final, October 2026) sets federal transition horizons for affected finite-field DH uses. |
| Deprecation Timeline | No universal commercial date. NIST IR 8547 (final, October 2026) is NIST guidance, not a commercial mandate; CNSA 2.0 dates are scoped to NSS and related contexts. |
| Replaced By | ML-KEM (FIPS 203) |
Algorithm-level classification. Standards status and known cryptanalysis are separated from implementation, module-validation, protocol-composition, key-management, and policy evidence.
Evidence-scope review: 2026-07-10
Replace DH/DHE with ML-KEM (FIPS 203) for key encapsulation. Use hybrid mode during transition.
QScout discovers instances of Diffie-Hellman across your infrastructure within the approved engagement window — designed to minimize operational disruption. First-findings timing is set during operator scoping.