# Do SSH and VPNs support post-quantum key exchange?

Increasingly, yes, but you have to check each product. OpenSSH made a hybrid post-quantum key exchange its default in version 9.0 in 2022, and version 10.0 in 2025 made the ML-KEM-based hybrid mlkem768x25519-sha256 the default; if both ends run current releases, your SSH sessions probably already use it. For VPNs the picture varies. The IPsec key exchange IKEv2 gained a standard way to add extra key exchanges, such as ML-KEM, in RFC 9370, and some vendors and open-source projects support it while others have only announced it. WireGuard can add a pre-shared symmetric key as an extra post-quantum protection layer, but its handshake itself is classical. Check the release notes of your firewall or VPN gateway firmware and the client versions actually in use, and remember that an old server at one end keeps the whole connection classical. Remote-access and site-to-site VPNs carry a lot of long-lived data, so they deserve a high place in your migration order.

FAQ: [Post-quantum cryptography](https://netsenx.com/en/faq/pqc) · https://netsenx.com/en/faq/do-ssh-and-vpns-support-post-quantum-key-exchange

## Read next

- https://netsenx.com/en/encrypted-traffic-analysis
- https://netsenx.com/en/features
- https://netsenx.com/en/blog/2026-10-27_harvest-now-decrypt-later

## Related questions

- [How can we find where we use quantum-vulnerable cryptography?](https://netsenx.com/en/faq/how-to-find-quantum-vulnerable-cryptography)
- [Can a network sensor build a cryptographic inventory?](https://netsenx.com/en/faq/can-a-network-sensor-build-a-cryptographic-inventory)
- [How do I find which connections already use hybrid key exchange?](https://netsenx.com/en/faq/which-connections-already-use-hybrid-key-exchange)
- [What should a cryptographic inventory include?](https://netsenx.com/en/faq/what-should-a-cryptographic-inventory-include)
- [Does NetSenX protect us against quantum computers?](https://netsenx.com/en/faq/does-netsenx-protect-us-against-quantum-computers)