Go standard library crypto

Go's built-in crypto and crypto/tls packages.

Ready

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

Ecosystem
Go
Homepage
pkg.go.dev
Repository
github.com/golang/go
Last verified

What to do

hybrid TLS key exchange: Go standard library crypto 1.24 or later. ML-KEM and ML-DSA: 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][2]–?No
ML-DSA
FIPS 204
Supported[3][4]–??
SLH-DSA
FIPS 205
Unknown–––
Hybrid TLS
e.g. X25519MLKEM768
Supported[5][6]1.24YesNo

Roadmap

No public roadmap recorded.

FIPS validation (PQC)

Unknown.

Libraries that rely on Go standard library crypto

Evidence

  1. tls package - crypto/tls - Go Packages · docs · retrieved 2026-11-13
    ML-KEM-768 (0x0041)
  2. Issue #82488: crypto/hpke: hybrid PrivateKey.Bytes returns the key's internal seed slice instead of a copy · issue · retrieved 2026-11-13
    {"MLKEM768", hpke.MLKEM768()}
  3. tls package - crypto/tls - Go Packages · docs · retrieved 2026-11-09
    MLDSA44 SignatureScheme = 0x0904
  4. PR #82302: crypto/internal/fips140/mldsa: compute cs1 and cs2 lazily when signing · pull request · retrieved 2026-11-09
    Sign/ML-DSA-44 266.4µ ± 0% 234.4µ ± 1% -12.00% (p=0.000 n=20)
  5. tls package - crypto/tls - Go Packages · docs · retrieved 2026-11-13
    From Go 1.24, the default includes the [X25519MLKEM768] hybrid
  6. tls package - crypto/tls - Go Packages · docs · retrieved 2026-11-13
    X25519MLKEM768 CurveID = 4588

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

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