The Libreswan Project vulnerabilities
We track 5 vulnerabilities in The Libreswan Project products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on October 13, 2026.
Latest The Libreswan Project vulnerabilities
- 7.5 High severity
libreswan: Use After Free
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 t
- 7.5 High severity
libreswan: Unchecked Return Value
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 CERT_PKCS7_WRAPPED_X509, it guards the PKCS#7 blob with SEC_PKCS7ContainsCertsOrCrls() and then iter
- 7.5 High severity
libreswan: NULL Pointer Dereference
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 a
- 7.5 High severity
libreswan: Unchecked Return Value
In FIPS mode, Libreswan's add_decoded_cert() function calls CERT_ExtractPublicKey() and asserts that the result is not NULL. However, CERT_ExtractPublicKey() returns NULL when public key extraction fails, for example if the RSA exponent is set to 0. A remote a
- 7.5 High severity
libreswan: Off-by-one Error
An invalidly formatted IKEv2 fragment causes the Libreswan pluto daemon to crash and restart. Continued exploitation would cause a denial of service. The function reassemble_v2_incoming_fragments() would ignore unknown outer payloads but still store these in a