BoringSSL

Google's fork of OpenSSL, used in Chrome and Android.

Ready

PQC is supported in a stable release and enabled by default where it applies (for example, hybrid key exchange on by default).

Ecosystem
C / C++
Homepage
boringssl.googlesource.com
Repository
github.com/google/boringssl
Last verified

What to do

ML-KEM, ML-DSA, SLH-DSA and hybrid TLS key exchange: supported in current releases; the sources don't state the first version. On by default: hybrid TLS key exchange.

Algorithm support

AlgorithmSupportSinceOn by defaultExperimentalNotes
ML-KEM
FIPS 203
Supported[1]–?No
ML-DSA
FIPS 204
Supported[2]–?No
SLH-DSA
FIPS 205
Supported[3]–?No
Hybrid TLS
e.g. X25519MLKEM768
Supported[4]–YesNo

Roadmap

No public roadmap recorded.

FIPS validation (PQC)

Unknown.

Notes

BoringSSL is not intended for general use and makes no API or ABI stability guarantees, so it has no numbered releases to compare against.

Libraries that rely on BoringSSL

Evidence

  1. https://raw.githubusercontent.com/google/boringssl/main/ssl/ssl_key_share.cc · docs · retrieved 2026-11-13
    {NID_ML_KEM_1024, SSL_GROUP_MLKEM1024, "MLKEM1024", ""},
  2. include/openssl/mldsa.h · other · retrieved 2026-11-11
    // This implements the Module-Lattice-Based Digital Signature Standard from // https://csrc.nist.gov/pubs/fips/204/final
  3. include/openssl/slhdsa.h · other · retrieved 2026-11-11
    // SLH-DSA-SHA2-128s public key.
  4. ssl/ssl_key_share.cc · other · retrieved 2026-11-11
    static const uint16_t kDefaultSupportedGroupIds[] = { SSL_GROUP_X25519_MLKEM768,

Out of date? Ask us to re-check BoringSSL against its latest releases, or suggest a correction or edit the data file on GitHub.

Machine-readable: /api/libraries/boringssl.json · Data from PQC Deps, CC BY 4.0.