Loading vulnerability…
CVE-2026-43967 is an inefficient algorithmic complexity vulnerability in the absinthe GraphQL toolkit for Elixir. The flaw is in Elixir.Absinthe.Phase.Document.Validation.UniqueFragmentNames:run/2, which validates fragment-name uniqueness by iterating over all fragments and, for each fragment, invoking duplicate?/2. That helper performs Enum.count(fragments, &(&1.name == name)), causing a full linear scan of the fragment list for each fragment processed. As a result, validation runs in O(N²) time with respect to the number of fragment definitions in the supplied GraphQL document. Because input.fragments is derived directly from the attacker-supplied query body, an attacker can fully control N by submitting a document containing a very large number of minimal fragment definitions. The issue affects absinthe versions from 1.2.0 before 1.10.2.
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.
3 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.