Unauthenticated crash via cloned identity double-free
Published Aug 22, 2026 · Updated Aug 22, 2026
Double-free in strongSwan 4.3.3 through 6.0.6 allows remote attackers to crash the IKE daemon via an empty EAP identity. The identification_t clone() method copies an empty, non-NULL encoding pointer without cloning it, so two identity objects free the same allocation. Unauthenticated reachability requires EAP, or IKEv1 XAuth with xauth-eap; a daemon crash is confirmed, while code execution remains unconfirmed.
Summary
What happened
Double-free in strongSwan 4.3.3 through 6.0.6 allows remote attackers to crash the IKE daemon via an empty EAP identity. The identification_t clone() method copies an empty, non-NULL encoding pointer without cloning it, so two identity objects free the same allocation. Unauthenticated reachability requires EAP, or IKEv1 XAuth with xauth-eap; a daemon crash is confirmed, while code execution remains unconfirmed.
The record
- CVE
- CVE-2026-47895
- Published
- Aug 22, 2026
- Updated
- Aug 22, 2026
- Vendor
- strongSwan
- Product
- strongSwan
- Classifications
- CWE-415, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4..3.3 <6.0.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo