FIPS 140-2 Sunsets Sept 21: The Hidden PQC Deadline
FIPS 140-2 certificates go Historical on Sept 21, 2026, and the FIPS 140-3 PQC backlog leaves vendors caught in between.
Mark your calendar for September 21. Not because it’s dramatic. Because it’s the opposite of dramatic, which is exactly why most security teams haven’t noticed it yet.
On that date, NIST’s Cryptographic Module Validation Program moves every remaining active FIPS 140-2 certificate to Historical status. No press conference, no CVE number, no vendor advisory blast. Just a quiet status flip in a government database that a lot of procurement contracts happen to reference by name.
What actually changes on September 21
FIPS 140-2 modules have been on a five-year clock for a while: validate, then age out or get revalidated. September 21, 2026 is the date CMVP finishes clearing the shelf. Every module still holding an active FIPS 140-2 validation on that day gets reclassified as Historical, regardless of when it was originally certified.
Historical doesn’t mean dead. Systems already running a Historical module can keep running it, and agencies can keep operating what they’ve already deployed. What Historical means is that CMVP no longer considers the module acceptable for new procurement. If you’re selling into the federal government, or into any of the contractors and cloud providers who inherit federal crypto requirements by extension, a Historical validation stops being a box you can check on a new deal. Only FIPS 140-3 satisfies that box going forward.
That would be a manageable, if annoying, compliance calendar item on its own. It’s the collision with post-quantum cryptography that makes it worth an article.
Why this is a PQC story and not just a paperwork story
FIPS 140-3 is the only validation track that covers NIST’s post-quantum algorithms. ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) all get validated as part of a module’s FIPS 140-3 submission, not as some separate add-on process. So the same September deadline that pushes vendors off FIPS 140-2 is also the deadline that, in theory, should be pulling them toward PQC-capable crypto.
In practice it isn’t working that way, because CMVP’s queue doesn’t move at the speed of a calendar deadline. Getting a module through FIPS 140-3 validation, even without post-quantum algorithms in scope, has been running well past a year for a lot of vendors. Adding ML-KEM or ML-DSA support to that submission adds testing surface, not less. Estimates I’ve seen from vendors actually in the queue put a fully PQC-capable FIPS 140-3 validation at 12 to 18 months out from a standing start, and that’s assuming nothing gets kicked back for revision, which is optimistic.
So here’s the actual situation a lot of vendors are in this month: their FIPS 140-2 module just went Historical, they need something FIPS 140-3 validated to keep selling into federal accounts, and the fastest path to that is submitting a classical-only module and dealing with post-quantum algorithms in a later revalidation cycle. The deadline that was supposed to nudge the industry toward quantum-safe crypto is, for a lot of vendors, producing another round of ECDSA and RSA modules with a new FIPS number on them. The infrastructure ends up compliant and exactly as vulnerable to harvest-now-decrypt-later as it was in August.
Where this leaves the rest of the timeline
Executive Order 14412 sets its own separate clocks: post-quantum encryption for high-value federal systems by the end of 2030, post-quantum authentication by the end of 2031. Those dates aren’t touched by what happens to FIPS 140-2 this month. But the CMVP backlog is now a real dependency sitting between here and there, and it’s not one any individual agency or vendor controls. A team that assumed “we’ll be fine once our vendor gets FIPS 140-3 certified” needs to check what’s actually in that vendor’s submission, because a validated module and a quantum-safe module are not automatically the same thing anymore.
If you’re on the buying side, this is worth a direct question to every vendor whose crypto touches a federal-adjacent system: is your current or pending FIPS 140-3 validation classical-only, or does it include ML-KEM and ML-DSA support, and if not yet, what’s the actual date on the revalidation that adds them. “We’re FIPS 140-3 validated” answers a different question than the one you’re asking, and after September 21 it’s an easy detail to gloss over because the compliance box does technically get checked either way.
The takeaway
September 21 will come and go without much noise, and most of the modules that flip to Historical that day will keep running in production for years, which is by design. The part worth tracking isn’t the sunset itself. It’s whether the FIPS 140-3 validations replacing those Historical modules are quietly extending the classical-crypto status quo or actually closing the post-quantum gap. Right now, for most of the industry, it’s the former. Ask your vendors which one you’re getting before you check the compliance box and move on.