CVE-2026-43967: falha de alta gravidade em absinthe-graphql absinthe
Quadratic fragment-name uniqueness check causes denial of service in absinthe
Publicada em · Atualizada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 8.7epss 0.6%
Inefficient Algorithmic Complexity vulnerability in absinthe-graphql absinthe allows unauthenticated denial of service via quadratic fragment-name uniqueness validation.
Absinthe.Phase.Document.Validation.UniqueFragmentNames.run/2 iterates over all fragments and for each one calls duplicate?/2, which evaluates Enum.count(fragments, &(&1.name == name)) — a full linear scan of the fragment list. The result is O(N²) comparisons per document, where N is the number of fragment definitions supplied by the caller.
Because input.fragments is built directly from the GraphQL query body, N is fully attacker-controlled. A minimum-size fragment definition is roughly 16 bytes, so a ~1 MB document carries ~60,000 fragments and forces ~3.6 × 10⁹ comparisons inside this single validation phase. No authentication, schema knowledge, or special configuration is required.
This issue affects absinthe: from 1.2.0 before 1.10.2.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Produtos afetados
absinthe-graphql · absintheCVEs relacionadas — absinthe-graphql absinthe
No mesmo produto, das mais perigosas para as menos.
Referências
https://cna.erlef.org/cves/CVE-2026-43967.htmlhttps://github.com/absinthe-graphql/absinthe/commit/0b46e3bcc06c0d3797bacd64761b908a84646c1dhttps://github.com/absinthe-graphql/absinthe/commit/223600c520493dcaf95080af552c413099f92c9dhttps://github.com/absinthe-graphql/absinthe/security/advisories/GHSA-9mhv-8h52-q7q2https://osv.dev/vulnerability/EEF-CVE-2026-43967