CVE-2026-94453

IKEv2 Use-After-Free bug when using IKE-over-TCP

  • High 7.5

Description

Libreswan's pluto daemon has a use-after-free vulnerability when a client connecting using IKE over TCP closes the connection and another packet (retransmit or malicious) is received for the same tuple. IKE state is retained in memory after the client closes the connection, storing a pointer to iface_endpoint inside ike_sa.sa->st_iface_endpoint. Once this invalid pointer is used, the daemon crashes and restarts. This vulnerability can be triggered before the remote peer has authenticated itself. Continued exploitation can lead to a denial of service. Remote code execution could be possible. The IKE over TCP option is not enabled by default; only configurations that contain listen-tcp=yes are affected.

Key facts

Published
13 Oct 2026
Last changed
16 Oct 2026
Assigned by
libreswan
EPSS
0.454% likely to be exploited in the next 30 days, higher than 40.086% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (libreswan)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
The Libreswan Projectlibreswan
  • Default status: unaffected
  • 4.0 up to and including 5.3.2 (affected)
  • 5.4 up to and including 5.4 (affected)
  • 5.3.3 (unaffected)
  • 5.4.1 (unaffected)

Timeline

  1. 16 Sep 2026 Libreswan was notified of the issue via security@libreswan.org
  2. 24 Sep 2026 Advanced notice given to supported customers and distributions
  3. 5 Oct 2026 Public announcement and release of libreswan 5.3.3 and 5.4.1
  4. 13 Oct 2026 Published

Weakness

References