CVE-2026-47895 is a critical memory-corruption vulnerability in the libstrongswan component of strongSwan, affecting versions since 4.3.3. The flaw is in the identification_t class clone() handling of certain identities with an empty but non-NULL encoding. The cloning logic copies the full object before updating the encoded chunk, and it checks the chunk length instead of the pointer when deciding whether to duplicate the encoding. As a result, an empty but non-NULL chunk may remain shared between the original and cloned identity objects, causing both objects to reference the same memory. When the objects are later destroyed, this can trigger a double-free. The issue is reachable during authentication flows that use the vulnerable identity constructors, particularly EAP and EAP-Identity exchanges, and can be triggered by processing an empty identity string with specific hex-encoded prefixes. The resulting condition can crash the daemon and may be exploitable for unauthenticated remote code execution on exposed VPN servers.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.