Java (OpenJDK) security providers
The JDK's built-in cryptography (JCA/JCE) and TLS (JSSE).
Partial
Only some algorithms are supported (for example, KEM but not signatures), or support is experimental or behind flags.
What to do
ML-KEM and ML-DSA: supported in current releases; the sources don't state the first version.
Algorithm support
Roadmap
No public roadmap recorded.
FIPS validation (PQC)
Unknown.
Libraries that rely on Java (OpenJDK) security providers
- Nimbus JOSE + JWT Planned
- Apache HttpClient Delegates
- gRPC Java Delegates
- OkHttp Delegates
- JJWT Unknown
Evidence
- JEP 496: Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism · docs · retrieved 2026-11-09
Provide ML-KEM implementations of the KeyPairGenerator, KEM, and KeyFactory APIs, with support for the parameter sets ML-KEM-512, ML-KEM-768, and ML-KEM-1024 standardized in FIPS 203.
- JEP 497: Quantum-Resistant Module-Lattice-Based Digital Signature Algorithm · docs · retrieved 2026-11-09
Provide ML-DSA implementations of the KeyPairGenerator, Signature, and KeyFactory APIs, with support for the parameter sets ML-DSA-44, ML-DSA-65, and ML-DSA-87 standardized in FIPS 204.
Out of date? Ask us to re-check Java (OpenJDK) security providers against its latest releases, or suggest a correction or edit the data file on GitHub.
Machine-readable: /api/libraries/openjdk.json · Data from PQC Deps, CC BY 4.0.