
2026-11-11
Bouncy Castle Java 1.87 is now available. This release extends post-quantum cryptography to OpenPGP, MLS and HPKE, adds controls for managing the migration away from quantum-vulnerable algorithms, introduces DTLS 1.3, and makes several algorithms dramatically faster.
The release continues Bouncy Castle's alignment with the latest NIST and IETF standards, giving organisations on post-quantum migration roadmaps a single, portable Java code base to build on.
OpenPGP and MLS previously had no standard post-quantum algorithms to move to, leaving encrypted mail, files and group messages exposed to harvest-now-decrypt-later collection. Release 1.87 implements RFC 9980 (Post-Quantum Cryptography in OpenPGP) in both the lightweight and JCA operators, adds the eleven post-quantum MLS cipher suites of draft-ietf-mls-pq-ciphersuites, and extends HPKE with new ML-KEM hybrids. BCJSSE now offers the X25519MLKEM768 hybrid first by default, with no extra round trip. The MLS suites use placeholder private-use code points until IANA assigns them.
The new QuantumVulnerableConstraint applies the NIST IR 8547 timetable to RSA, DSA, DH, EC, EdDSA and X25519/X448: allowed, then logged after 2030, then refused after 2035 except for verification and decryption. It is installed through the org.bouncycastle.constraints.quantum_vulnerable property and defaults to "none", so nothing is refused unless a deployment opts in. Post-quantum algorithms now report their NIST security category through PQCParameters, and the generated CBOM marks quantum-vulnerable assets at security level 0.
The low-level TLS API now implements DTLS 1.3 (RFC 9147), including DTLS-SRTP, for IoT, media and VPN vendors. It is opt-in, and some features, such as 0-RTT and connection IDs, are not yet implemented. BCJSSE adds delegated handshake tasks for SSLEngine (off by default in this release) and the BCSSLContext and BCSSLServerSocket interfaces, which makes it easier to use in non-blocking frameworks such as Netty and Vert.x.
With outputs unchanged and constant-time behaviour kept, the SM9 pairing runs about 120 to 145 times faster, NTRU Prime encapsulation and decapsulation about 30 to 40 times faster, and BLS12-381 signing about 12 to 18 times faster. ChaCha20-Poly1305 and BLAKE3 are also faster, and the first signature from a fresh LMS key at height 15 drops from 2.6 seconds to about a millisecond. Customers get these gains by upgrading, with no API changes.
HQC now follows the HQC team's specification of 2026-10-12, the one on the path to FIPS 207, so keys and ciphertexts from earlier releases are not compatible. The SP 800-232 Ascon algorithms and the SP 800-56C one-step KDF are in the BC provider, with javax.crypto.KDF services on Java 25. The provider's SecureRandom accepts DrbgParameters, and ML-KEM and ML-DSA keys from other providers are now accepted. Classic McEliece is deprecated as it is no longer believed safe to use.
Fixes for the following CVEs:
For the complete list of added features, fixed security issues, and defects, see:
Bouncy Castle Java 1.87 is available on Maven Central and at bouncycastle.org/download. SBOM files are published alongside the release on Maven Central.

