OESA-2026-4931: libreswan security update
Libreswan is an implementation of IKEv1 and IKEv2 for IPsec. IPsec is the Internet Protocol Security and uses strong cryptography to provide both authentication and encryption services. These services allow you to build secure tunnels through untrusted networks. Everything passing through the untrusted net is encrypted by the ipsec gateway machine and decrypted by the gateway at the other end of the tunnel. The resulting tunnel is a virtual private network or VPN. Security Fix(es):
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.steap which is NULL. A malicious IKEAUTH 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.(CVE-2026-77206)
Libreswan has a null pointer dereference bug in the PKCS#7 handling code for IKE certificate authentication. When libreswan decodes an IKE CERT payload of type CERTPKCS7WRAPPEDX509, it guards the PKCS#7 blob with SECPKCS7ContainsCertsOrCrls() and then iterates the certificate list with SECPKCS7GetCertificateList(). The two NSS APIs disagree on a SignedData that carries a CRL but no certificates: ContainsCertsOrCrls() returns PRTRUE (there is a CRL), so the guard passes, but GetCertificateList() returns NULL (there are no certificates). This causes libreswan to dereference a null pointer leading to a crash and restart. A malicious IKEAUTH packet can trigger this bug, meaning the peer does not need to be authenticated. No remote code execution is possible. Continued exploitation can cause a denial of service.(CVE-2026-77207)
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 ifaceendpoint inside ikesa.sa->stifaceendpoint. 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.(CVE-2026-94453)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/libreswanto a version that resolves this vulnerability.Fixed in 4.15-5.oe2203sp4 - Configuration
For configurations with listen-tcp=yes, set listen-tcp=no to disable the affected IKE-over-TCP option.
Libreswan listen-tcp = no
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
Do IKEv2 deployments that do not use EAP need to be concerned?
Yes. The IKEv2 state-machine flaw can be triggered by any IKEv2 connection, even when EAP is not configured.
What must an attacker have to trigger the IKEv2 flaw?
An attacker only needs to send a malicious IKE_AUTH packet to a reachable IKEv2 service. The peer does not need to authenticate first.
What is the practical impact of successful exploitation?
The flaw crashes and restarts the pluto daemon. Repeated exploitation can cause a denial of service; remote code execution is not possible from this issue.