CVE-2026-115846: IKEv2: IKE_INTERMEDIATE exchange bypass error
The Libreswan IKEv2 state machine did not verify that an IKEINTERMEDIATE exchange was required to satisfy the addke= PostQuantum algorithm component of the exchange. A connecting client could (maliciously or by implementation error) skip the IKEINTERMEDIATE exchange and start an IKEAUTH 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Libreswanto a version that resolves this vulnerability.Fixed in 5.4.2
Event History
Frequently Asked Questions
Which deployments are affected?
Only Libreswan IKEv2 connections configured with the addke= keyword in the ike= and/or esp= option are affected. PostQuantum Hybrid Key Exchange support, and therefore this exposure, was added in version 5.4.
What must happen for the weaker protection to be used?
A connecting client must skip the required IKE_INTERMEDIATE exchange and initiate IKE_AUTH prematurely, either maliciously or because of an implementation error. The state machine accepts this flow rather than enforcing the additional key-exchange component.
What is the practical security impact?
The connection is protected only by its classic key exchange algorithm, such as P-256 or Curve25519, as though addke= had not been configured. Recorded traffic could therefore be subject to store-now-decrypt-later attacks if sufficiently capable quantum computers become available.