Java 27 Ships Post-Quantum Cryptography That Protects Your Apps Without Changing a Line of Code

by Geth Author

JDK 27 shipped on September 15, 2026, and its headline feature lands squarely in infrastructure security: post-quantum hybrid key exchange for TLS 1.3, built directly into the standard library and requiring zero code changes for most Java applications already using the platform's SSL APIs.

What JEP 527 Actually Does

The centerpiece of this release is JEP 527, which adds ML-KEM — a post-quantum key encapsulation mechanism standardized as NIST FIPS 203 — to TLS 1.3 via a hybrid scheme. "Hybrid" means it combines ML-KEM with a classical key exchange algorithm (X25519), so a connection remains secure against both classical and quantum attackers simultaneously. If a quantum computer eventually cracks the classical component, the quantum-resistant part holds. If ML-KEM has an unforeseen flaw, the classical component still protects you.

Any Java application using the javax.net.ssl APIs — which covers the vast majority of Java HTTPS clients and servers — gets this protection automatically when running on JDK 27. You update the JDK, not your code.

Performance Improvements Across the Board

JDK 27 also delivers significant performance gains for the post-quantum algorithms themselves: ML-KEM and ML-DSA are measurably faster than in prior releases, and those improvements extend to classical algorithms X25519 and Ed25519. Private key encodings for ML-KEM and ML-DSA have been updated for better interoperability across implementations. The full release includes 9 JEPs spanning language, performance, and security dimensions.

Why the Timing Matters

"Harvest now, decrypt later" attacks — where adversaries collect encrypted traffic today to decrypt once a capable quantum computer exists — are a documented and serious threat model for governments, financial institutions, and large enterprises. Post-quantum cryptography in TLS is the defense. Java's deployment scale means JDK 27 moves the needle for a non-trivial share of the world's backend infrastructure the moment organizations upgrade.

NIST finalized its first set of post-quantum cryptography standards in 2024. JDK 27 ships those standards as a first-class, default-on feature of the Java TLS stack. That's the right way for an ecosystem this large to handle a coming security inflection point: make the safe path the automatic path.

JDK 27 General Availability builds are available now from inside.java. For teams still on JDK 25 (the current LTS), earlier ML-KEM and ML-DSA primitives are available — but JEP 527's hybrid TLS integration is exclusive to JDK 27 for now.