Bouncy Castle (Java)
Cryptography APIs and JCA provider for Java.
Available
PQC is supported in a stable release, but you have to opt in.
What to do
ML-KEM, ML-DSA and SLH-DSA: Bouncy Castle (Java) 1.79 or later. hybrid TLS key exchange: Bouncy Castle (Java) 1.81 or later. On by default: hybrid TLS key exchange.
Algorithm support
Roadmap
No public roadmap recorded.
FIPS validation (PQC)
Unknown.
Libraries that rely on Bouncy Castle (Java)
- Nimbus JOSE + JWT Planned
Evidence
- https://raw.githubusercontent.com/bcgit/bc-java/main/docs/releasenotes.md · release notes · retrieved 2026-11-17
The ML-KEM KeyGenerator, Cipher, javax.crypto.KEM and KeyFactory.translateKey services accepted only BC's own key objects, breaking BCJSSE handshakes over the ML-KEM groups when another provider supplied the key.
- https://raw.githubusercontent.com/bcgit/bc-java/main/docs/releasenotes.md · release notes · retrieved 2026-11-17
The ML-DSA and SLH-DSA KeyFactory.translateKey refused keys from other providers, such as the JDK's ML-DSA keys; they are now converted from their encoding.
- Bouncy Castle release notes, 1.81 · release notes · retrieved 2026-11-11
- BCJSSE: Draft support for hybrid ECDHE-MLKEM (draft-ietf-tls-ecdhe-mlkem-00).
- Bouncy Castle release notes, 1.86 · release notes · retrieved 2026-11-11
NamedGroupInfo's default candidate list, which applies when jdk.tls.namedGroups is not set, gains SecP256r1MLKEM768 and SecP384r1MLKEM1024, appended so the classical groups keep their existing preference.
Out of date? Ask us to re-check Bouncy Castle (Java) against its latest releases, or suggest a correction or edit the data file on GitHub.
Machine-readable: /api/libraries/bouncycastle-java.json · Data from PQC Deps, CC BY 4.0.