Skip to content
Threat Brief

← All advisories

CVE-2026-53426

High 8.2No known exploitationFix available

Atom-table exhaustion denial-of-service via JSON parse_document in MDEx

Record last updated

CVSS score

8.2

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 8% 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 leandrocp MDEx allows Excessive Allocation. MDEx.parse_document/2 accepts a {:json, json} source. In lib/mdex.ex, the private json_to_node/1 function passes the attacker-controlled node_type value to Module.concat/1, which calls String.to_atom/1 and interns a brand-new atom for every distinct value. Atoms are never garbage collected on the BEAM, so a crafted JSON document carrying a unique node_type at each (deeply nested) node mints one permanent atom per node. A single document can intern hundreds of thousands of atoms, and a large enough document exhausts the default atom table (around 1,048,576 atoms) and aborts the entire Erlang VM, taking down every process on the node. Any application that passes untrusted input to the {:json, ...} source of MDEx.parse_document is exposed to an unauthenticated denial-of-service. This issue affects mdex: from 0.4.3 before 0.13.2.

Weakness: CWE-770

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
Do not pass untrusted or attacker-controlled input to the {:json, ...} source of MDEx.parse_document/2. The {:markdown, ...} source is not affected. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
leandrocpmdexfrom 0.4.3 before 0.13.20.13.2CVE Program
leandrocpmdexfrom cbb59a3f792dbc343873adec3466f49c853dc309 before 00fddf444220a1f1cc0af0a1cab673880487838700fddf444220a1f1cc0af0a1cab6738804878387CVE 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