CVE-2026-77206

IKEv2 pre-authentication Null Pointer Dereference in EAP code

  • High 7.5

Description

Libreswan's IKEv2 state machine has a null pointer dereference bug in the EAP handling code for authentication. As a result of inconsistency within the IKEv2 state machine code, this bug can be triggered by any IKEv2 connection, even if EAP is not configured at all. The error is caused by a fall-through where it incorrectly dereferences ike->sa.st_eap which is NULL. A malicious IKE_AUTH packet can trigger this bug, meaning the peer does not need to be authenticated. The bug results in a crash and restart of the pluto daemon. No remote code execution is possible. Continued exploitation can cause a denial of service.

Key facts

Published
13 Oct 2026
Last changed
16 Oct 2026
Assigned by
libreswan
EPSS
0.658% likely to be exploited in the next 30 days, higher than 52.24% 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.7 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. 5 Aug 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