post quantum vpn vpn with post quantum encryption post quantum cryptography vpn

Post-quantum VPN: what it is and what it protects

Adrian Maverick · · 7 min read

A post-quantum VPN is a VPN that agrees its encryption keys with a method designed to resist quantum computers, usually alongside the classic method it already used. The point is to stop traffic recorded today from being decrypted years from now, when a large enough quantum computer may exist.

It does not change what a VPN is for. It closes one specific gap: the moment when your device and the VPN server agree on a secret key over an open network.

What makes a VPN "post-quantum"?

Every VPN connection has two parts. First, your device and the server agree on a shared secret key. Then they use that key to encrypt everything you send.

The second part, the bulk encryption, uses symmetric ciphers with long keys, which quantum computers are not expected to break. The first part is the weak spot. Most VPNs agree keys using elliptic-curve math, and a large quantum computer could solve that math and recover the key.

WireGuard, the protocol behind most current VPN apps, says this about itself on its known limitations page: "WireGuard is not, by default, post-quantum secure."

A post-quantum VPN adds a key exchange built on different math, one that has no known quantum shortcut. The VPN tunnel and the encryption of your traffic stay the same. Only the way the key is agreed changes.

Why it matters now: harvest now, decrypt later

Nobody has a quantum computer that can break today's key exchange. So why bother?

Because encrypted traffic can be recorded now and kept. If the key exchange can be broken later, every recorded session can be opened later too. This is known as harvest now, decrypt later, a phrase that also appears in the guidance collected on CISA's quantum page.

WireGuard's designer named this threat in the original WireGuard paper: "adversaries may be recording encrypted traffic on a long term basis, in hopes of someday being able to break Curve25519 and decrypt past traffic."

A VPN tunnel is an especially tempting thing to record, because one stream carries a lot: browsing, app traffic, logins, messages. Protection only helps if it is on before the traffic is sent. Turning it on in ten years does nothing for what was recorded today.

For the wider background, see what is post-quantum encryption and will quantum computers break encryption.

ML-KEM: the standard behind post-quantum VPNs

In August 2024, NIST published FIPS 203, the Module-Lattice-Based Key-Encapsulation Mechanism Standard. It defines ML-KEM, the algorithm formerly known as CRYSTALS-Kyber. NIST's announcement calls FIPS 203 "the primary standard for general encryption."

ML-KEM is a key-encapsulation mechanism, which FIPS 203 describes as a way for two parties to "establish a shared secret key over a public channel." That is exactly the job a VPN needs done at the start of a connection. NIST's summary adds: "At present, ML-KEM is believed to be secure, even against adversaries who possess a quantum computer."

FIPS 203 has three strength levels: ML-KEM-512, ML-KEM-768 and ML-KEM-1024, in order of increasing security strength. When you read a VPN's post-quantum claim, the name of the algorithm and the level are the first things to look for.

Hybrid key exchange: why use both

Serious post-quantum VPNs do not throw away the classic key exchange. They run both and combine the results. This is called a hybrid key exchange.

The reasoning is simple. To read the traffic, an attacker has to break both methods:

  • If a quantum computer breaks the classic elliptic-curve exchange, the ML-KEM part still protects the key.
  • If a flaw is ever found in the newer ML-KEM math, the classic exchange still protects the key against today's attackers.

You keep the protection you already trust and add a second, quantum-resistant layer. Neither one has to be perfect on its own.

How post-quantum works with WireGuard

WireGuard has a built-in place for this. Its protocol page describes an optional pre-shared key that is "mixed into the public key cryptography" for "post-quantum resistance." When the key is not used, WireGuard fills the slot with 32 zero bytes.

The WireGuard project's own advice, again from its known limitations page, is: "The best bet for post-quantum security is to run a truly post-quantum handshake on top of WireGuard, and then insert that key into WireGuard's pre-shared key slot."

So a post-quantum WireGuard VPN works like this:

  1. The app and the server run a post-quantum key exchange, such as ML-KEM.
  2. The secret that comes out of it is loaded into WireGuard's pre-shared key slot.
  3. WireGuard runs its normal elliptic-curve handshake, with that secret mixed in.

The result is a hybrid by design. For the full detail, including how the key is delivered and how to check a tunnel yourself, see is WireGuard quantum-safe.

What a post-quantum VPN protects, and what it does not

Protected by post-quantum key exchange?
Recorded VPN traffic being decrypted later by a quantum computer Yes, this is what it is for
Your traffic between your device and the VPN server today Yes, as with any well-built VPN
Data on websites and services you sign in to No, that depends on each service
Traffic after it leaves the VPN server for the website No, that depends on the website's own encryption
Malware or phishing on your device No
Tracking by accounts you are signed in to No

Post-quantum key exchange is about the future reading the present. It protects the tunnel. It does not change what a VPN does or does not hide, which we cover in what does a VPN hide.

How to check a VPN's post-quantum claim

"Quantum-safe" on a website is not an answer. These four questions are:

  1. Which algorithm, at which level? "ML-KEM-1024" or "ML-KEM-768" is an answer. "Quantum-grade encryption" is not.
  2. Is it hybrid? The post-quantum exchange should be added to the classic one, not replace it.
  3. Is it on by default? A setting you have to find protects only the people who find it.
  4. Does it cover every server, device and plan? Check whether it switches off with certain protocols, features or apps.

A VPN that has built this properly will say so in writing. If its documentation cannot answer the first question, treat the claim as unproven.

Frequently asked questions

Do I need a post-quantum VPN?

It depends on how long your traffic needs to stay private. Because recorded traffic can be decrypted later, protection only helps if it is on now. For anything that would still matter in ten years, it is worth having today.

Does a post-quantum VPN slow down my connection?

The post-quantum exchange happens when you connect. Your traffic is then encrypted with the same symmetric cipher as before, so day-to-day browsing works the same way. Our post on whether a VPN slows down your internet covers the factors that do matter.

Is a post-quantum VPN the same as quantum encryption?

No. Post-quantum cryptography is ordinary software math that runs on today's phones and computers and is designed to resist quantum attacks. It needs no quantum hardware.

Is WireGuard post-quantum?

Not by default, in WireGuard's own words. It becomes post-quantum resistant when a post-quantum key is loaded into its pre-shared key slot.

What is the strongest ML-KEM level?

ML-KEM-1024, the highest of the three parameter sets in FIPS 203.

Post-quantum in Secria VPN

Secria VPN uses WireGuard with an ML-KEM-1024 post-quantum key added to every session, on by default. Every plan gets the same encryption, Free included. You can read how we built it in our launch post.

If you want to try a VPN without paying, Secria VPN Free works on iPhone, iPad, Mac and Android with a free Secria account, no card needed. Free servers are in Frankfurt and Dallas, one device at a time, and it runs on RAM-only servers: keys, configs and connection state are never written to disk. No activity logs: we do not record browsing, DNS queries or traffic contents. Paid plans add every location, Multi-Hop, split tunneling and 5 devices. See pricing.

Secria fact-checks every post against primary sources. Spotted something wrong or out of date? Email hq@secria.me and we will correct it.