Oracle Plans Post-Quantum TLS for Java 8 and 11 in Late 2027, and Wants Testers Now

Oracle Plans Post-Quantum TLS for Java 8 and 11 in Late 2027, and Wants Testers Now

BackerLeader ●58 ●371 ●548
calendar_today • schedule4 min read

Security teams are starting to ask a question platform teams don't like: what's our plan for post-quantum encryption? For shops still running Java 8 or 11, the answer has mostly been a shrug.

At Oracle AI World in Las Vegas this week, I got a firmer one. I sat down with Georges Saab, senior vice president of Oracle's Java Platform Group; Donald Smith, vice president of product management for Java Platform; and Bernard Traversat, vice president of software development for the Java Platform Group. I asked about the schedule for hybrid post-quantum key exchange in TLS 1.3.

The feature is generally available in JDK 27. It arrived in JDK 25 with the October critical patch update. I laid out what comes next as I understood it: Java 21 and 17 in the first half of 2027, Java 11 and 8 in the second half. The team confirmed that was right.

Those are half-year windows, not release dates. And there is a condition attached.

Customers have been asking Oracle for post-quantum support as fast as possible. Now that it ships, the team wants them to use it. Many reply that they'd rather have it backported first. Oracle's answer is to test what already exists.

Smith said the key to stability is "just getting people using what we have, even though it's only in the latest."

There is a chicken-and-egg problem. The specification was only finalized in February, so many of the endpoints a Java client talks to don't support the hybrid exchange yet. Smith called the backport itself the hard part. For the next two to three months, the team is focused on stability so the backport starts from solid ground.

Feedback comes from two places. One is customers. The other is a group in OpenJDK that works with major third-party library projects, including Apache and Eclipse, and with the OpenSSL community.

Performance is the other worry. Java 8 shipped years before TLS 1.3 was final, and the team had to backport it. That taught them the backport has to be stable and fast on old hardware. A team tracks performance benchmarks on every release, including the new algorithms, he said. He gave no numbers.

If you run Java 8 or 11, waiting for the backport and then starting your testing is the slow path. Point a JDK 25 or 27 client at your post-quantum-capable endpoints, such as a gateway or proxy, and report what breaks. Oracle says it needs that feedback.

Backports aren't the only way out. Saab said he now regularly meets teams where most workloads are on Java 21.

He described the upgrade ladder this way. Going from 8 to 11 is the hardest step. Each step after that gets easier. "21 to 25 super easy," he said. The platform has been changed so that code survives upgrades better than it used to.

When teams do get stuck, the cause is usually outside the JDK. One is third-party libraries that nobody maintains. The other is the oldest problem: "when people used APIs that were not part of the public API," Saab said.

For finding those problems, Traversat pointed to Oracle's Java Management Service. It analyzes the APIs an application uses and reports deprecated APIs, changed behavior, and JVM argument changes between versions, such as 11 to 17 or 25. After that, he said, you still run the testing you use to certify the application.

I also asked how a team should verify code that an AI agent has refactored. Smith was direct: "I don't have a swift answer for that one." Saab said migration tooling is being built by other people. His team has helped groups inside Oracle migrate, to learn what the JDK could do better. Would the JDK team build migration tools itself? "I'm not saying we will never do that," he said.

So if you plan to use agents on a legacy Java codebase, the tools will come from outside the JDK. Verification still falls to your test suite.

The other date on your calendar is the patch schedule. Oracle announced in the spring that it is moving to monthly security updates across the company, not just for Java. Smith said the Java team will phase this in. "Next year we'll probably do 10 security updates and then it'll be every month thereafter," he said.

AI is part of the reason. "It's clear that AI has increased the rate at which you find vulnerabilities," Smith said. He added that it has also improved the team's ability to fix them.

He worried at first that system administrators would push back. They haven't. "The feedback is like nobody is surprised by this," he said. Some organizations will still have to adapt. A team on a quarterly change window is the obvious example.

Two items have no dates: non-hybrid key exchange and Merkle certificates. Smith said the work follows the IETF specifications and he wasn't sure enterprises could plan around it. His advice was to follow OpenJDK development. The issue trackers are open, and code already exists.

That caution is deliberate. "Never get ahead of the spec," Smith said. He pointed to the original java.util.Date as the example. An early implementation gained traction, it wasn't the best design, and the proper replacement took 10 to 15 years to arrive. Traversat added that anything shipped in the platform has to be supported for years, so Oracle moves conservatively.

For Java teams, the planning date is the second half of 2027 for Java 8 and 11. The work that decides whether that date holds starts now, and Oracle is asking for your help.

Want more #java & #appsec deep dives?

Join 5,941+ developers sharing real benchmarks, code breakdowns, and projects. Free forever.

More Posts

AAIF Hits 10 Projects. Its CTO on What to Adopt Now and the Security Gaps Left Open

Tom Smithverified - Oct 23

Faceted Navigation and Pagination for Ecommerce SEO

floxolab - Aug 31

PHP2Shell: Two 9.2-Rated Flaws Reach Back to PHP 5. Here's the Plan for EOL Teams

Tom Smithverified - Oct 22

Your Kubernetes Requests Are a Guess. groundcover Wants an Agent to Keep Fixing Them.

Tom Smithverified - Nov 3

Apollo Pricing: Plans, Credits, and Real Small-Team Cost

floxolab - Aug 29
chevron_left
20.9k Points • 977 Badges
287Posts
171Comments
141Connections
LLM Training & Evaluation Specialist with hands-on experience building major AI models. As one of th... Show more

Related Jobs

View all jobs →

Commenters (This Week)

5 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!