CVE-2026-35330 is a vulnerability in libsimaka involving the processing of certain EAP-SIM/AKA attributes. According to the provided context, malformed or specially crafted attributes can trigger either an infinite loop or a heap-based buffer overflow during parsing or handling of EAP-SIM/AKA data. The heap corruption condition may potentially lead to remote code execution. Specific vulnerable functions, affected versions, and patch details are not available in the provided content.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Small repository containing a single live C proof-of-concept exploit (`poc.c`), a README, and a GPL license. The PoC targets CVE-2026-35330 in strongSwan's EAP-SIM/AKA attribute parser. It is not a remote exploit harness by itself; instead, it locally links against installed `libsimaka.so` and `libstrongswan.so` and directly exercises the public API `simaka_message_create_from_payload()` followed by `msg->parse(msg)`. The crafted payload is a minimal 12-byte EAP-SIM message with an `AT_RAND` TLV whose length field is zero. This causes `hdr->length * 4 - 4` to underflow in `parse_attributes()`, leading to malformed allocation/copy behavior in `add_attribute()` and a heap buffer overflow/crash on vulnerable versions. The repository is clearly a PoC rather than a weaponized exploit: there is no shellcode, persistence, command execution, or post-exploitation logic. Its main capability is vulnerability triggering and crash demonstration, useful for validation and defensive testing. Although the underlying bug is pre-auth and reachable from network-delivered EAP-SIM/AKA traffic in real deployments, the included code demonstrates it through local library invocation rather than sending packets to a live endpoint.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.