CVE-2026-115846 · Infrastructure
NO FIX YET
Libreswan's IKEv2 handling does not check that the post-quantum IKE_INTERMEDIATE exchange happened before authentication, so a client can skip it. The connection then falls back to classic key exchange only, which a future quantum computer could break to decrypt recorded traffic.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only Libreswan IKEv2 connections that set the addke= option in the ike= or esp= configuration are affected. Servers and gateways without addke= configured are not exposed to this flaw. The sources give no fixed version for this CVE.
Not affected if libreswan-before-5.4, no-addke-configured
Who cares ipsec, libreswan, self-hosted, vpn
addke= in the ike= or esp= settings of Libreswan connection configs (ipsec.conf or /etc/ipsec.d/*.conf)ipsec --version, comparing against the fixed version in the sources (unknown)No fix yet, per the sources.
The Libreswan IKEv2 state machine did not verify that an IKE_INTERMEDIATE exchange was required to satisfy the addke= PostQuantum algorithm component of the exchange. A connecting client could (maliciously or by implementation error) skip the IKE_INTERMEDIATE exchange and start an IKE_AUTH exchange prematurely. The result is as if the addke= option had not been specified, and such connections are only protected by the classic key exchange algorithm (such as P-256 or Curve25519), allowing "store now, decrypt later" attacks once a quantum computer becomes available. Only connections with the addke= keyword in the ike= and/or esp= configuration option are affected. PostQuantum Hybrid Key Exchange support was added in version 5.4.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.