Source context: this article examines information published by the source on November 04, 2026. This site’s publication date is shown separately. Check the latest vendor guidance before acting.
What was published
On November 4, 2026, NIST announced a planned revision to Special Publication (SP) 800-108r1, “Recommendation for Key Derivation Using Pseudorandom Functions.” This announcement serves as a pre-draft call for comments, requesting public feedback by December 18, 2026.
Status and scope
The guidance is currently in the pre-draft phase. It is not a finalized standard or a mandatory requirement at this time. The scope of the revision focuses on key-derivation constructions that utilize pseudorandom functions (PRFs), specifically targeting areas where recent cryptanalytic research has raised security concerns.
What the guidance covers
The planned revision is driven by research identifying issues with output indistinguishability and key-control security. NIST intends to address several specific technical areas:
* Construction Updates: Updating constructions that have been affected by recent cryptanalytic results.
* CMAC-based Constructions: Reconsidering existing guidelines for those using Cipher-based Message Authentication Code (CMAC).
* Double-Pipeline Iteration Mode: Evaluating whether this specific mode remains necessary.
* Security Properties: Clarifying the expected security properties required of key-derivation functions.
How organizations can use it
Infrastructure owners and vulnerability management teams should treat this announcement as an early warning signal for cryptographic technical debt. While no immediate patch is available—as the revised constructions are not yet finalized—organizations can use this information to identify where SP 800-108r1 is currently implemented within their environment.
Defenders should focus on identifying assets that rely on CMAC-based constructions or Double-Pipeline Iteration Mode. This allows for a prioritized inventory of cryptographic dependencies, ensuring that when the final revision is published, the organization can move quickly to validate and update affected systems.
Decisions and next steps
Our analysis suggests the following decision checkpoints for security leaders:
1. Inventory Cryptographic Assets: Identify all internal and third-party systems utilizing NIST SP 800-108r1 for key derivation.
2. Categorize Exposure: Specifically flag implementations using CMAC or Double-Pipeline Iteration Mode, as these are explicitly mentioned as targets for reconsideration.
3. Vendor Inquiry: For proprietary hardware or software, query vendors on their adherence to SP 800-108r1 and their roadmap for adopting the upcoming revision.
4. Monitor Finalization: Establish a trigger to review the final publication of the revised standard against the identified asset list to determine necessary remediation.
Limits and open questions
Because this is a pre-draft call for comments, the specific updated constructions have not been finalized. Consequently, it is not possible to verify if a current implementation is “secure” or “vulnerable” based on this notice alone.
There remains uncertainty regarding the exact nature of the cryptanalytic results mentioned and how they translate to real-world exploitability in diverse environments. Furthermore, since the revised standard is not yet published, organizations cannot yet implement a verified fix; they can only prepare for one.
Source and editorial note
Pre-Draft Call for Comments: Key Derivation Using Pseudorandom Functions November 04, 2026 · Source date: November 04, 2026 · Retrieved November 04, 2026.
Material facts are tied to the cited primary source. Recommendations are independent defensive analysis unless attributed to the source. Confirm consequential decisions against current authoritative guidance.
Request a Vulnerability Assessment
Turn security intelligence into action.
Discuss your exposure, priorities, and the evidence needed to validate the outcome.
Request a security assessment ↗