CVE-2026-47895: strongSwan EAP-Identity parsing double-free in libstrongswan

CVE-2026-47895 · Severity: high · CVSS 7.5 · Published 2026-08-22

strongSwan is an open-source VPN and IPsec suite widely used for secure network communications. A flaw in how identity data is parsed and cloned in the EAP authentication module can cause a double-free memory error, potentially leading to a remote denial of service or code execution if an attacker can influence EAP identity parsing.

Technologies: strongSwan. Vendors: strongSwan.

Quick answers

Is CVE-2026-47895 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47895 being exploited in the wild.
How severe is CVE-2026-47895?
High severity, with a CVSS score of 7.5, published 22 August 2026.
Which products and versions are affected?
strongSwan 4.3.3 through 6.0.6.
Is there a fix for CVE-2026-47895?
A patch was published on 2026-06-08: Fixed in strongSwan 6.0.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47895 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-47895?
Check whether you run strongSwan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a double-free defect in libstrongswan's identity cloning logic. When EAP-Identity data is parsed and results in an empty but non-NULL encoded value, the cloning mechanism fails to properly duplicate the identity object. This causes the same memory location to be freed twice when duplicate identities are destroyed, leading to heap corruption. The flaw affects all strongSwan versions 4.3.3 through 6.0.6. An attacker can trigger the vulnerability during EAP authentication negotiation by supplying specially crafted identity payloads. Patch available in strongSwan 6.0.7 and later.

Affected products

  • strongSwan strongSwan 4.3.3 through 6.0.6

Timeline

  • 2026-08-22: disclosed
  • 2026-06-08: patched: Fixed in strongSwan 6.0.7

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.