Secuno
ENNL
Book demo

CVE-2026-42793

Absinthe-graphql Absinthe denial of service

7.5 HIGHPublic exploitEPSS 0.70%
  1. Published8 May 2026

Description

Allocation of Resources Without Limits or Throttling vulnerability in absinthe-graphql absinthe allows unauthenticated denial of service via atom table exhaustion when parsing attacker-controlled GraphQL SDL. Multiple Blueprint.Draft.convert/2 implementations in Absinthe's SDL language modules call String.to_atom/1 on attacker-controlled names from parsed GraphQL SDL documents, including directive names, field names, type names, and argument names. Because atoms are never garbage-collected and the BEAM atom table has a fixed limit (default 1,048,576), each unique name permanently consumes one slot. An attacker can exhaust the atom table by submitting SDL documents containing enough unique names, causing the Erlang VM to abort with system_limit and taking down the entire node. Any application that passes attacker-controlled GraphQL SDL through Absinthe's parser is exposed — for example, a schema-upload endpoint, a federation gateway that ingests remote SDL, or any developer tool that runs the parser over user-supplied documents. This issue affects absinthe: from 1.5.0 before 1.10.2.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Absinthe-graphql Absinthe> 1.5.0 < 1.10.2

Remediation

Fixed in
Absinthe-graphql Absinthe≥ 1.10.2

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1031028.6
Pexip Infinity before 41.0 is affected by improper input validation in the signaling…
CVE-2026-1031018.6
Pexip Infinity 30.0 through 40.x before 41.0 is affected by improper input validation…
CVE-2026-824399.8
Description The DRPC server kept a map from function name to request queue and created…
CVE-2026-478919.8
A Spring WebFlux application that relies on the Aalto XML processor to parse XML input…
CVE-2026-735418.2
Allocation of Resources Without Limits or Throttling in ZenHive mpp allows an…
CVE-2026-748789.8
openssl_encrypt versions before 1.4.0 use an in-memory rate limiter for TOTP…

Frequently asked

Is CVE-2026-42793 being actively exploited?

CVE-2026-42793 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.70%.

How severe is CVE-2026-42793?

CVE-2026-42793 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.70% probability of exploitation.

Which products are affected by CVE-2026-42793?

Affected products include Absinthe-graphql Absinthe.

How do I fix CVE-2026-42793?

Upgrade affected software to a fixed version, for example Absinthe-graphql Absinthe 1.10.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-42793 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.