Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-35330: Heap-based buffer overflow in libsimaka EAP-SIM/AKA attribute processing

Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-35330CWE-122

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may cause denial of service via an infinite loop and may also enable memory corruption through a heap-based buffer overflow. In the more severe case, the provided context indicates the vulnerability could potentially be leveraged for remote code execution.

Mitigation

If you can’t patch tonight, do this now.

Until vendor remediation information is available, limit exposure of systems or services that process untrusted EAP-SIM/AKA messages through libsimaka, restrict access to trusted peers where possible, and monitor for crashes or hangs associated with malformed authentication traffic. Additional mitigation guidance is currently not available in the provided content.

FAQ

Frequently asked questions

Is CVE-2026-35330 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-35330 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35330?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-35330, the earliest disclosed May 14, 2026.
Activity feed

Recent activity

4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.