CVE-2026-43967
Unauthenticated DoS in Absinthe GraphQL via fragment-name validation.
Is CVE-2026-43967 being exploited?
Not confirmed. CVE-2026-43967 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-43967?
CVE-2026-43967 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-43967?
Yes. A fix has been recorded for CVE-2026-43967. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43967 affect?
CVE-2026-43967 affects absinthe-graphql (Elixir) 1.2.0–1.10.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43967?
Upgrade to Absinthe 1.10.2+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled GraphQL input with many fragments causes O(N^2) validation, leading to DoS.
Patch when possible
- affected>= 1.2.0 and < 1.10.2
- affected>= 0b46e3bcc06c0d3797bacd64761b908a84646c1d and < 223600c520493dcaf95080af552c413099f92c9d
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.