wolfSSL Adds Post-Quantum Support for SEALSQ’s QVault TPM

SEALSQ and wolfSSL announced that wolfTPM now supports SEALSQ’s QVault post-quantum TPM. This integration allows embedded developers to access the chip’s NIST-standardized algorithms through software. According to the companies, the integration successfully passed wolfSSL’s PQC test suite, both on physical QVault hardware and in a firmware TPM environment. 

This release provides software support for a chip that is not yet shipping, which means it’s not a currently available product. This information originates from a company press release.

Collaboration Between the Two Companies

Specifically, wolfTPM, wolfSSL’s TPM 2.0 library, now includes code to recognize and configure the QVault device via SPI. Developers will receive a new command-line tool, pqc_ctrl, along with examples, build instructions, and hardware benchmarks. This tool exposes the chip’s supported algorithms and facilitates self-tests.

The integrated algorithms are ML-DSA and ML-KEM, which are lattice-based signature and key-encapsulation schemes that NIST standardized as FIPS 204 and FIPS 203, respectively. The release also includes support for Hash-ML-DSA. These are established standards, and their integration represents the credible aspect of this announcement. Testing encompassed ML-DSA signing and verification, as well as ML-KEM encapsulation and decapsulation, across all supported key strengths.

Jean Pierre Enguent, SEALSQ CTO, articulated the purpose of this work in the release:

“QVault implements post-quantum algorithms directly in TPM hardware, while wolfTPM provides the embedded software support needed to use them.”

Distinguishing Claims from Facts

SEALSQ characterizes QVault as “on track to be the first shipping TPM 2.0 device on the market” to incorporate post-quantum algorithms from the Trusted Computing Group’s TPM 2.0 v1.85 specification into silicon. The terms “on track” and “first” are the company’s own and are forward-looking. This announcement doesn’t confirm that the chip is currently shipping, so the “market first” label describes a future plan.

The security rationale is that private keys remain within the TPM. Todd Ouska, wolfSSL CTO, stated in the release that executing ML-DSA and ML-KEM within the chip ensures keys are generated and used in hardware, never crossing the TPM boundary. This is a sound design objective for a hardware security module; however, the release doesn’t offer independent certification data, nor does it claim FIPS 140-3 module validation.

No cryptographically relevant quantum computer (CRQC), capable of breaking current encryption, currently exists. Products like this address the “harvest-now-decrypt-later” risk, where data captured today could be decrypted in the future. The code is available as a pull request on wolfSSL’s GitHub for developer inspection. SEALSQ is traded on Nasdaq as LAES. No pricing, ship date, or shipment volume details were disclosed.