NIST’s 2026 Post-Quantum Signature Update: Standards, Candidates, and Limited-Use SLH-DSA Explained

Bottom line

A security team skimming NIST’s 2026 post-quantum signature updates could easily make one bad spreadsheet mistake: putting a finalized standard, an evaluation candidate, and a public-comment draft in the same “approved algorithms” column.

That is the wrong reading. The useful question is not “Did NIST mention this algorithm?” It is “What kind of NIST document is this?”

Item	Status	What it means	Mistake to avoid
FIPS 204	Final standard	The finalized NIST standard for ML-DSA	Treating ML-DSA as part of the May 2026 candidate list
FIPS 205	Final standard	The finalized NIST standard for SLH-DSA	Treating SLH-DSA as only a draft or new 2026 candidate
Nine additional signature schemes	Third-round candidates	Algorithms still under NIST evaluation	Treating advancement as approval
SP 800-230	Initial public draft	Proposed additional SLH-DSA parameter sets for limited-use cases	Treating the comment deadline as a compliance deadline

The practical rule is simple: read the document status before reading the algorithm name.

What happened

On May 14, 2026, NIST announced that nine candidates had advanced to the third round of its process for additional post-quantum digital signatures. The candidates are FAEST, HAWK, MAYO, MQOM, QR-UOV, SDitH, SNOVA, SQIsign, and UOV.

The word “advanced” matters. These schemes moved into another evaluation round; they were not finalized as standards. NIST’s announcement says the selection followed 18 months of evaluation and that third-round candidates may submit updated specifications and implementations. NIST also said it expects the third round of evaluation and review to take about two years.

Separately, NIST has an initial public draft, SP 800-230, about additional SLH-DSA parameter sets for limited signature use cases. That draft is tied to SLH-DSA, not to the nine candidate schemes.

So this is not one announcement with one operational meaning. It is a document-status sorting problem.

Evidence level

The evidence base here is official NIST material: the May 2026 NIST announcement, NIST IR 8610, the SP 800-230 initial public draft, the finalized FIPS 204 standard, and the finalized FIPS 205 standard.

That source mix is strong for document status. It is not enough to conclude which third-round candidate will become a standard, whether SP 800-230 will remain unchanged, or whether a particular organization should deploy a specific parameter set.

The finalized baseline is FIPS 204 plus FIPS 205

For post-quantum digital signatures, the baseline in this discussion is not FIPS 205 alone.

FIPS 204 is the Module-Lattice-Based Digital Signature Standard. It specifies ML-DSA, a digital signature algorithm derived from the CRYSTALS-Dilithium submission to NIST’s post-quantum cryptography standardization project.

FIPS 205 is the Stateless Hash-Based Digital Signature Standard. It specifies SLH-DSA, which is based on SPHINCS+.

Those two FIPS documents are finalized standards. They are different from a NIST internal report, different from a candidate list, and different from an initial public draft.

This distinction is where I would slow down in any internal review. “NIST post-quantum signature” is not a status label. ML-DSA in FIPS 204, SLH-DSA in FIPS 205, a third-round candidate, and a draft parameter extension each mean something different.

The nine schemes are still candidates

NIST IR 8610 describes the second-round evaluation and the selection of candidates for the third round. It also frames any additional signature schemes selected in the future as complementing existing documents such as FIPS 204, FIPS 205, FIPS 186-5, and SP 800-208.

That “complementing” frame is important. The current materials do not support saying that the third-round candidates replace ML-DSA or SLH-DSA, or that they are ready to be listed internally as approved standards.

A careful internal status line would look like this:

Field	Safer wording
Algorithms	FAEST, HAWK, MAYO, MQOM, QR-UOV, SDitH, SNOVA, SQIsign, UOV
NIST status	Additional digital signature third-round candidates
Operational reading	Track NIST evaluation and later standardization decisions
Avoid writing	Final standard, approved algorithm, immediate deployment target

The friction point is ordinary but real: once a candidate gets copied into a roadmap without its status label, later reviewers may assume a decision has already been made.

SP 800-230 is about limited-use SLH-DSA parameters

SP 800-230 is titled “Additional SLH-DSA Parameter Sets for Limited Signature Use Cases.” NIST describes it as a technical extension of FIPS 205.

That means SP 800-230 is not a new signature family competing with the nine third-round candidates. It is a draft extension around SLH-DSA parameter choices.

The draft proposes six additional parameter sets across security levels 1, 3, and 5. The purpose is to address cases that need faster verification and reduced signature size. The draft’s examples include software, firmware, and digital certificate signing.

The catch is not a footnote. According to the draft, the optimization depends on a strict limit of 2^24 signatures per signing key. Because of that limit, the parameter sets are not approved for general-purpose use.

That changes the engineering question. The first question is not “Are smaller signatures useful?” It is “Can the system reliably enforce the signing limit over the full lifetime of the key?”

June 12, 2026 is a comment deadline

The SP 800-230 page lists June 12, 2026 as the date comments are due. That is a public comment deadline for the initial public draft.

It is not a compliance deadline. It is not a required migration date. It is not a date by which products must adopt the proposed parameter sets.

For internal notes, write the date this way:

Risky shorthand	More accurate wording
SP 800-230 deadline	SP 800-230 public comment deadline
Limited-use SLH-DSA adoption date	Comment deadline for a draft about limited-use SLH-DSA parameters
New PQC signature migration schedule	One step in NIST’s draft review process

Dates create urgency. In standards work, that urgency is useful only if the date is attached to the right action.

What changes if readers classify the documents correctly

The update becomes much less confusing once each item is sorted by status.

For students and researchers, the nine schemes are a map of what NIST is still evaluating in additional post-quantum signatures.

For security engineers, FIPS 204 and FIPS 205 are the finalized post-quantum signature standards in this source set: ML-DSA under FIPS 204 and SLH-DSA under FIPS 205. SP 800-230 is a draft extension to examine with its usage limits intact.

For technology buyers or policy readers, the main takeaway is that “NIST mentioned it” is not the same as “NIST finalized it.” Procurement language, architecture notes, and compliance trackers should preserve the difference.

What remains uncertain

The cited sources do not tell us which, if any, of the nine third-round candidates will become final standards. They also do not establish that SP 800-230’s proposed parameter sets will appear unchanged in a final document.

They also do not answer whether limited-use SLH-DSA parameters fit a particular deployment. That depends on security review, key management, signing volume, auditing, implementation maturity, and the ability to enforce the 2^24 signatures-per-key limit.

The safer line is to treat SP 800-230 as a draft to review, not as a shortcut around the harder operational questions.

What to watch next

First, keep the standards separate from the moving pieces: FIPS 204 for ML-DSA, FIPS 205 for SLH-DSA, the May 2026 candidate announcement for third-round evaluation, and SP 800-230 for draft limited-use SLH-DSA parameters.

Second, watch the SP 800-230 public comment process. The relevant date is June 12, 2026, and the action attached to it is comment submission.

Third, watch for updated specifications and implementations from the nine third-round candidates. At this stage, the details of the specifications and NIST’s later evaluation matter more than the mere presence of a candidate name on the list.

A clean tracker should have separate rows for FIPS 204, FIPS 205, NIST IR 8610, the candidate announcement, and SP 800-230. That one habit prevents most of the confusion: status first, algorithm second, operational limits third.