Skip to content
Threat Brief

← All advisories

CVE-2026-77206

High 7.5No known exploitationFix available

IKEv2 pre-authentication Null Pointer Dereference in EAP code

Record last updated

CVSS score

7.5

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.7%

Higher than 52% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-476

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
Apply the available patch or upgrade to a supported version. No configuration-based workaround is available. Source (opens in a new tab)
Vendor guidance
libreswan.org (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl4 libreswan 5.4-6.azl4 on Azure Linux 4.0Not documented0:5.4.1-4.azl4Microsoft MSRC
The Libreswan Projectlibreswanfrom 4.7 up to and including 5.3.2Not documentedCVE Program
The Libreswan Projectlibreswanfrom 5.4 up to and including 5.4Not documentedCVE Program
The Libreswan Projectlibreswan (unaffected)5.3.3Not documentedCVE Program
The Libreswan Projectlibreswan (unaffected)5.4.1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by libreswan

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references