The cryptographic landscape in 2026 sits in a strange place. The algorithms everyone trusts are slowly becoming the algorithms nobody should trust, and the algorithms everyone should trust are still too new to deploy at scale. The migration has started, but the gap has not closed. The honest framing matters here, because the practitioner who pretends the gap does not exist will end up filing the breach disclosure that the migration was supposed to prevent.
What follows serves as the working version of the Q2 state. The full report runs longer. The shorter version is what the working security engineer actually has time to read.
What is happening with post quantum
Three things, in roughly that order of how much each one matters in Q2 2026. The first runs as the NIST standards finalised, with the FIPS 203 (ML-KEM, the key encapsulation), the FIPS 204 (ML-DSA, the digital signature), the FIPS 205 (SLH-DSA, the hash based signature) all now in the final form, the standards sit ready to use. The second runs as the vendor implementations arrived, with the major TLS libraries (the OpenSSL 3.5, the BoringSSL, the RustTLS) now shipping the post quantum key exchange as the default, the hybrid key exchange sits in the browser, the server stack, the cloud provider. The third runs as the federal deadline landed, with the CNSA 2.0 timeline requiring the post quantum migration for the national security systems by 2030, the commercial deadline for the broader federal systems by 2035, the deadline that looked theoretical in 2024 now running as a procurement constraint in 2026.
What is happening with everything else
Three things, in roughly that order of how much each one should worry the practitioner. The first runs as the RSA key size problem, where the RSA 2048 key that everyone uses is still secure against the classical computer, but the margin has narrowed, the 2048-bit key that served as the default for twenty years is now the floor, the 3072-bit and 4096-bit keys are the new default for the high value certificate. The second runs as the SHA-1 collision risk, where the SHA-1 that everyone deprecated in 2017 still appears in the legacy certificate, the legacy code signing path, the legacy firmware, the SHA-1 collision attack runs as a real risk for the system that has not finished the migration. The third runs as the random number generator weakness, where the implementations that rely on the predictable entropy source (the embedded device, the IoT firmware, the older virtual machine) produce the keys that the attacker can predict, the random number generator that served as the implementation detail in 2010 now serves as the attack surface in 2026.
What the practitioner should do
Three moves if you are the practitioner who wants to land the cryptographic migration without breaking the production system. Inventory the certificates, because the certificate inventory serves as the foundation for every other move, the inventory finds the certificates that are still on SHA-1, the inventory finds the certificates that are still on RSA 1024, the inventory gives the practitioner the migration list. Turn on the hybrid key exchange at the edge, because the hybrid (the X25519 plus ML-KEM) gives the practitioner the post quantum protection without breaking the client, the cloud provider already supports it, the edge appliance already supports it, the only thing missing runs as the configuration. Audit the entropy source, because the weak entropy produces the weak key, the weak key produces the breach the cryptographic migration was supposed to prevent, the entropy audit costs a day and finds the device that needs the fix. The practitioner who inventories the certificates, turns on the hybrid key exchange, and audits the entropy source serves as the practitioner who lands the migration without breaking the production system.
The bottom line
The cryptographic state in Q2 2026 sits in a transition. The post quantum standards are ready, the classic algorithms are weakening, the entropy problem still lurks in the embedded fleet. The practitioner who inventories, turns on the hybrid, and audits the entropy holds the line. The one who waits for the deadline does not.
Sources & Further Reading
All claims in this article are sourced from primary documentation, vendor advisories, and reputable security researchers.
Spotted an error? Email the editor. Corrections are issued with a visible correction note.
Editorial standards. Every article on humanrequired.org is reviewed by a human editor before publication. AI may assist with drafting or research; final editorial control is human. Read the full standards.
