Classical algorithms below 112-bit security strength
For Classical algorithms below 112-bit security strength, purpose is all purposes; current status is Disallowed; planned status is minimum moves from 112 bits to 128 bits at the end of 2030; replacement is algorithms at 128-bit security strength or higher; source document is SP 800-131A Rev 2 / Rev 3 draft, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- Classical algorithms below 112-bit security strength
- Purpose
- all purposes our reading
- Current status
- Disallowed our reading
- Planned status
- minimum moves from 112 bits to 128 bits at the end of 2030 our reading
- Replacement
- algorithms at 128-bit security strength or higher our reading
- Source document
- SP 800-131A Rev 2 / Rev 3 draft 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: Classical algorithms below 112-bit security strength — 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/classical-algorithms-below-112-bit-security-strength/, checked 2026-11-18.
What the source says
Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030
— encryptionconsulting.com, retrieved 2026-08-16
Source
- encryptionconsulting.comhttps://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/
Does your own code still call Classical algorithms below 112-bit security strength? 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