No. ECDH is not quantum safe. It relies on the same elliptic curve math as ECDSA and is fully broken by Shor's algorithm.
Key Takeaway: ECDH is NOT quantum safe. Inventory each ECDH path. Where an approved hybrid or ML-KEM profile is supported, test the exact endpoints, negotiation, combiner, downgrade, middleboxes, telemetry, and rollback before deployment.
ECDH is NOT quantum safe.
Elliptic Curve Diffie-Hellman (ECDH) is a key agreement protocol that allows two parties to establish a shared secret over an insecure channel. It is the elliptic curve variant of classical Diffie-Hellman, offering equivalent security with much smaller key sizes. A 256-bit ECDH key (Curve25519 or P-256) provides similar security to 3072-bit classical Diffie-Hellman, resulting in faster computations and smaller key exchange messages.
The protocol works as follows: Alice generates a private key (a random scalar a) and computes a public key (A = aG, where G is a generator point on the elliptic curve). Bob does the same (private key b, public key B = bG). They exchange public keys over an insecure channel. Alice computes the shared secret as aB = a(bG) = abG. Bob computes bA = b(aG) = abG. Both arrive at the same shared secret abG without ever transmitting it.
ECDH is ubiquitous in modern internet security: TLS 1.3 mandates ECDHE (ephemeral ECDH) for forward secrecy, using curves like X25519, P-256, or P-384. Signal, WhatsApp, and iMessage use ECDH (specifically X25519) for end-to-end encrypted messaging. SSH uses ECDH for session key establishment. WireGuard VPN uses Curve25519 for key exchange.
ECDH security depends on the elliptic curve discrete logarithm problem (ECDLP): given public keys A and B, it should be computationally infeasible to determine the private keys a or b, or to compute the shared secret abG without knowing a or b. Classically, solving ECDLP requires exponential time (approximately 2(n/2) operations for an n-bit curve, so 2128 for P-256).
Shor's algorithm breaks ECDLP in polynomial time. Fault-tolerant qubit, gate, and runtime estimates vary by curve, architecture, and error-correction assumptions; this page does not claim that ECDH will be broken before another public-key primitive.
Ephemeral keys provide classical forward secrecy after long-term key compromise, but a recorded ECDHE exchange remains within the HNDL threat model if a future adversary can solve the captured discrete-log instance. Exposure still depends on successful capture, protocol details, data lifetime, and future capability.
Organizations should inventory ECDH use and migrate through approved key-establishment profiles:
Implementation note: ML-KEM public keys and ciphertexts are larger than ECDH (ML-KEM-768 uses ~1,184 bytes vs. 32 bytes for X25519). Test for compatibility with network equipment, firewalls, and legacy systems that may have packet size limitations.
Financial systems should assess each ECDHE path for capture exposure, data lifetime, protocol profile, and migration readiness. A sector label does not prove every session is captured or establish a universal immediate deployment mandate.
Healthcare entities should derive confidentiality periods and safeguards from actual records, applicable law, contracts, and documented risk analysis. HIPAA does not impose a universal 50-year retention period or prescribe ML-KEM.
CNSA 2.0 requirements are scoped to NSS and related acquisition or interoperability contexts. Its December 2024 FAQ describes staged 2027 acquisition, 2030 phaseout, and 2031 algorithm-use dates unless otherwise noted; it is not a universal 2030 ML-KEM mandate.
Messaging and collaboration platforms (Slack, Microsoft Teams, Zoom, end-to-end encrypted messaging apps) use ECDH for establishing encryption keys. While consumer messages may have short confidentiality requirements, corporate communications, trade secrets, and M&A discussions retain value for years or decades.
Set transition dates from measured exposure, data lifetime, applicable policy, supported profiles, interoperability evidence, and rollback readiness.
| Full Name | Elliptic Curve Diffie-Hellman |
| Category | key exchange |
| Quantum Vulnerability | Shor's algorithm — ECDLP solved in polynomial time. HNDL risk for encrypted data with long confidentiality requirements. |
| NIST Status | NIST IR 8547 is an initial public draft describing proposed federal transition horizons for affected ECDH uses. |
| Deprecation Timeline | No universal commercial date. NIST IR 8547 remains an initial public draft; 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
Inventory each ECDH path. Where an approved hybrid or ML-KEM profile is supported, test the exact endpoints, negotiation, combiner, downgrade, middleboxes, telemetry, and rollback before deployment.
QScout discovers instances of ECDH across your infrastructure within the approved engagement window — designed to minimize operational disruption. First-findings timing is set during operator scoping.