finite-field Diffie-Hellman
For finite-field Diffie-Hellman, purpose is key establishment; current status is Approved; planned status is deprecated after 2030 and disallowed after 2035; replacement is ML-KEM (FIPS 203); source document is IR 8547, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- finite-field Diffie-Hellman verified
- Purpose
- key establishment our reading
- Current status
- Approved our reading
- Planned status
- deprecated after 2030 and disallowed after 2035 our reading
- Replacement
- ML-KEM (FIPS 203) our reading
- Source document
- IR 8547 our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
Cite as: finite-field Diffie-Hellman — NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when (NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when), referencesource.org/nist-cryptographic-algorithm-deprecation-schedule/finite-field-diffie-hellman/, checked 2026-11-18.
What the source says
Under NIST IR 8547, quantum-vulnerable public-key algorithms are deprecated after 2030 and disallowed after 2035. What are the NIST 2030 and 2035 deadlines? Under the NIST IR 8547 draft timeline, quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field Diffie-Hellman)
— encryptionconsulting.com, retrieved 2026-08-16
Source
- encryptionconsulting.comhttps://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/
Open the page on encryptionconsulting.com that states this — the page quoted above, at its publisher. Unpaid: we earn nothing from this link and it is not an advertisement.
Does your own code still call finite-field Diffie-Hellman? npx crypto-deprecation-check reads the places where naming an algorithm is the point of the line -- createHash, a JWT alg, Cipher.getInstance, MODE_ECB, generateKeyPair, createECDH, an SSH HostKeyAlgorithms setting, an openssl subcommand -- and prints the status we hold for each with this page's sentence quoted. It fails a build only on a status that is already deprecated or disallowed, says nothing at all about algorithms we hold no record for, and makes no network calls. crypto-deprecation-check on npm