Skip to content
Threat Brief

← All advisories

CVE-2026-67585

High 8.7No known exploitationFix available

Atom Exhaustion via _entities Representation Keys in DivvyPayHQ absinthe_federation

Record last updated

CVSS score

8.7

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.7%

Higher than 54% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Allocation of Resources Without Limits or Throttling vulnerability in DivvyPayHQ absinthe_federation allows an unauthenticated remote attacker to abort the Erlang VM via crafted _entities representation keys. Every key of every object in the representations argument of the federation-mandated _entities field is converted with String.to_atom/1 by convert_key/2 in lib/absinthe/federation/schema/entities_field.ex. representations is typed as the open-ended _Any scalar, so its keys bypass schema coercion and the attacker names them freely. Atoms are never garbage collected and the BEAM atom table is hard-capped (about 1,048,576 entries by default), so one request carrying tens of thousands of unique keys creates that many permanent atoms and a handful of such requests exhausts the table and aborts the node. The impact is confined to availability: no data is read or altered, and recovery requires restarting the application. This issue affects absinthe_federation: from 0.1.0 before 0.9.3.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
DivvyPayHQabsinthe_federationfrom 0.1.0 before 0.9.30.9.3CVE Program
DivvyPayHQabsinthe_federationfrom 640a234a26b2d6fe5d9d21e00e5f4fce5645c0bf before c3838cda2a7f65c4893291668c223b0d6acf4516c3838cda2a7f65c4893291668c223b0d6acf4516CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references