NIST's final post-quantum timeline: what changes for your code
NIST published the final version of IR 8547 on October 27, 2026. The dates match the draft, but the scope is wider: every strength of RSA and elliptic-curve encryption is now on the clock, not just the smallest keys.
The dates
IR 8547 covers the public-key algorithms that a large quantum computer could break with Shor's algorithm. In the final report, all of them follow the same two dates:
| Algorithm | Used for | Deprecated | Disallowed |
|---|---|---|---|
| RSA | Signatures, key transport | After 2030 | After 2035 |
| ECDSA, EdDSA (Ed25519) | Signatures | After 2030 | After 2035 |
| ECDH, X25519, finite-field DH | Key exchange | After 2030 | After 2035 |
Deprecated means still allowed, but you accept the risk of using it. Disallowed means it may no longer be used under NIST standards and guidelines.
What changed from the draft
The 2024 draft deprecated only the smallest approved keys after 2030, such as RSA-2048. Larger keys, like RSA-3072 and P-256, could carry on until 2035. The final report drops that split. In its words, NIST "will deprecate all quantum-vulnerable cryptography after 2030."
So moving from RSA-2048 to RSA-4096 no longer buys extra time. Bigger keys still matter today for security against ordinary computers, but they are not a quantum plan.
Federal deadlines are earlier still. The report cites Executive Order 14412, which requires the government's most sensitive systems to adopt post-quantum key establishment by December 31, 2030, and post-quantum signatures by December 31, 2031. If you sell software to federal agencies or their suppliers, expect those dates in your contracts first.
The replacements
- Key exchange: ML-KEM (FIPS 203). ML-KEM-768 is the usual default.
- Signatures: ML-DSA (FIPS 204), or SLH-DSA (FIPS 205) where you want a hash-based design.
- Hybrid: NIST allows combining a classical and a post-quantum method, so the result holds as long as either one does. For TLS, that is X25519MLKEM768.
Symmetric encryption and hashes are not the problem. AES and SHA-256 stay in place.
What to do first
1. Find out where your encryption lives
Most teams can't answer which services use RSA or elliptic curves, or for what. That list is the starting point for everything else. Our guide to finding quantum-vulnerable encryption in your code covers where to look and what to search for.
2. Move key exchange first
Anyone can record encrypted traffic today and decrypt it once a large quantum computer exists. Signatures don't have that problem: a forged signature only matters at the moment it's checked. So key exchange protecting data that must stay private for years comes first.
Much of this is an upgrade, not a rewrite:
- OpenSSL 3.5 and later offer X25519MLKEM768 in TLS by default.
- Go 1.24 and later enable X25519MLKEM768 in
crypto/tlswhen you leaveCurvePreferencesunset, and ship ML-KEM incrypto/mlkem. - Java 24 and later include ML-KEM and ML-DSA in the standard library.
Check for code that pins an older curve list, such as a hard-coded CurvePreferences in Go or an explicit curve setting in your web server. Pinning quietly opts you out of the hybrid default.
3. Plan signatures by key lifetime
Start with keys that live longest and are hardest to replace: firmware and code signing, root certificates, and anything baked into devices. Short-lived session tokens can follow your libraries as they add ML-DSA.
4. Fix what's weak today
MD5, SHA-1, DES, ECB mode and RSA-1024 are broken or weak right now, quantum or not. They are the quickest wins. See what to use instead.
2030 is close for this kind of work. Encryption tends to sit in shared libraries, configuration and vendor products that change slowly. The teams that start with an inventory now will spend the next four years on planned changes rather than a rush.
Keep the inventory current on every pull request
Hard Keel Quantum Scan is free. It flags leaked keys, weak encryption and encryption quantum computers will break in each pull request, and keeps a migration plan for the repository.
See how it works