The Workers Web Crypto API now supports ML-KEM-768, ML-KEM-1024, ML-DSA-44, ML-DSA-65, and ML-DSA-87. ML-KEM establishes shared secrets, while ML-DSA signs and verifies data.
The opt-in API also adds key encapsulation and decapsulation methods, getPublicKey(), SubtleCrypto.supports(), and JSON Web Keys (JWKs) with the AKP key type.
Turn on the webcrypto_modern_algorithms compatibility flag to use these features:
{
"$schema": "./node_modules/wrangler/config-schema.json",
"compatibility_flags": [
"webcrypto_modern_algorithms"
]
}
compatibility_flags = ["webcrypto_modern_algorithms"]
This example uses ML-KEM-768 to establish the same shared secret on both sides:
src/index.jsjs
const keyPair = await crypto.subtle.generateKey("ML-KEM-768", false, [
"encapsulateBits",
"decapsulateBits",
]);
if (!("publicKey" in keyPair)) {
throw new Error("Expected an ML-KEM key pair");
}
const { sharedKey, ciphertext } = await crypto.subtle.encapsulateBits(
"ML-KEM-768",
keyPair.publicKey,
);
const recoveredSharedKey = await crypto.subtle.decapsulateBits(
"ML-KEM-768",
keyPair.privateKey,
ciphertext,
);
src/index.tsts
const keyPair = await crypto.subtle.generateKey("ML-KEM-768", false, [
"encapsulateBits",
"decapsulateBits",
]);
if (!("publicKey" in keyPair)) {
throw new Error("Expected an ML-KEM key pair");
}
const { sharedKey, ciphertext } = await crypto.subtle.encapsulateBits(
"ML-KEM-768",
keyPair.publicKey,
); …