strongSwan vulnerabilities
We track 9 vulnerabilities in strongSwan products across 2 products. 9 are rated high or critical, and none are known to be exploited. The most recent was published on September 11, 2026.
Latest strongSwan vulnerabilities
- 7.3 High severity
strongSwan: Improper Enforcement of Behavioral Workflow
libcharon in strongSwan 5.9.7 through 6.0.7 mishandles behavioral workflow in the IKEv2 state machine. Because CREATE_CHILD_SA requests are mishandled, there can be an authentication bypass.
- 7.1 High severity
strongSwan: Incorrect Authorization
strongSwan 4.5.0 through 6.0.7 has Incorrect Access Control in the eap-ttls and eap-peap plugins because there can be a missing or mismatched inner EAP identity.
- 7.5 High severity
strongSwan: Double Free
In strongSwan before 6.0.7, identity parsing/cloning is mishandled. Parsed EAP-Identities that result in an empty but non-NULL encoding are not correctly cloned and trigger a double-free once the duplicates are destroyed.
- 7.5 High severity
strongSwan: Integer Underflow (Wrap or Wraparound)
strongSwan versions 4.5.0 prior to 6.0.5 contain an integer underflow vulnerability in the EAP-TTLS AVP parser that allows unauthenticated remote attackers to cause a denial of service by sending crafted AVP data with invalid length fields during IKEv2 authent
- 7.5 High severity
strongMan: Reusing a Nonce, Key Pair in Encryption
strongMan is a management interface for strongSwan, an OpenSource IPsec-based VPN. When storing credentials in the database (private keys, EAP secrets), strongMan encrypts the corresponding database fields. So far it used AES in CTR mode with a global database
- 8.1 High severity
strongSwan: Integer Underflow (Wrap or Wraparound)
In the eap-mschapv2 plugin (client-side) in strongSwan before 6.0.3, a malicious EAP-MSCHAPv2 server can send a crafted message of size 6 through 8, and cause an integer underflow that potentially results in a heap-based buffer overflow.
- 9.8 Critical severity
Strongswan: Buffer Copy without Checking Size of Input
strongSwan before 5.9.12 has a buffer overflow and possible unauthenticated remote code execution via a DH public value that exceeds the internal buffer in charon-tkm's DH proxy. The earliest affected version is 5.3.0. An attack can occur via a crafted IKE_SA_
- 9.8 Critical severity
Strongswan: Improper Certificate Validation
strongSwan 5.9.8 and 5.9.9 potentially allows remote code execution because it uses a variable named "public" for two different purposes within the same function. There is initially incorrect access control, later followed by an expired pointer dereference. On
- 7.5 High severity
Strongswan: Uncontrolled Resource Consumption
strongSwan before 5.9.8 allows remote attackers to cause a denial of service in the revocation plugin by sending a crafted end-entity (and intermediate CA) certificate that contains a CRL/OCSP URL that points to a server (under the attacker's control) that doe