Uncontrolled recursion over deeply nested Markdown crashes the BEAM in mdex
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: leandrocp mdex 0.12.3, 6ed94d905f97af188323f042698ae841c02293b4; leandrocp mdex_native 0.2.3, 947696c47bc22bea5dffc0f78c946fa6b70ce183.
Low priority for now. Upgrade to leandrocp mdex 0.12.3, 6ed94d905f97af188323f042698ae841c02293b4; leandrocp mdex_native 0.2.3, 947696c47bc22bea5dffc0f78c946fa6b70ce183 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Uncontrolled Recursion vulnerability in leandrocp mdex allows denial of service via deeply nested Markdown input. mdex converts between an Elixir %MDEx.Document{} struct and Comrak's internal AST using two mutually recursive Rust functions, ex_document_to_comrak_ast and comrak_ast_to_ex_document, in the NIF source file document.rs. Neither function enforces a maximum nesting depth, so the recursion depth is bounded only by the structure of the input. An attacker who can get a Markdown document rendered (for example through MDEx.parse_document!/1 or MDEx.to_html/1) can supply a document with thousands of nested block quotes, which drives unbounded recursion across the NIF boundary and exhausts the native C stack. Because the resulting stack overflow is an uncatchable SIGSEGV raised inside a NIF, it cannot be contained by the Erlang runtime. It terminates the operating system process running the BEAM, killing every Elixir and Erlang process on the node, not just the caller that triggered the render. No authentication or special privileges are required. The vulnerable conversion code was extracted from mdex into the separate mdex_native package starting in mdex 0.12.3. This issue affects mdex from 0.3.0 before 0.12.3 and mdex_native from 0.1.0 before 0.2.3.
- Published
- Jun 29, 2026
- Updated
- Jun 30, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-674
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
leandrocp mdex
- 0.3.0 and later · before 0.12.3affected · semver
- d0bc7d55177727c61d188ef465178ab3b81f4f2c and later · before 6ed94d905f97af188323f042698ae841c02293b4affected · git
leandrocp mdex_native
- 0.1.0 and later · before 0.2.3affected · semver
- 956528c5e31746253347029e810a969ab916fd27 and later · before 947696c47bc22bea5dffc0f78c946fa6b70ce183affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Hex | mdex | from 0.3.0 · before 0.12.3 | 0.12.3 |
| Hex | mdex_native | from 0.1.0 · before 0.2.3 | 0.2.3 |
Same product
leandrocp: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-53426Atom-table exhaustion denial-of-service via JSON parse_document in MDEx32Monitor
- CVE-2026-53429Unbounded native memory leak in mdex escaped-tag rendering enables unauthenticated denial of service27Monitor
- CVE-2026-53428Unbounded memory allocation in highlight_lines range expansion in mdex27Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-53427Jun 29, 2026 · Cross-site scripting in MDEx via unescaped highlight_lines_class code-fence attribute9Monitor
- Later →CVE-2026-54889Jun 29, 2026 · Unsanitized URL schemes in MDEx Quill Delta output allow javascript: injection (XSS)20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| leandrocp mdex | 0.12.3 | Vendor (CNA) |
| leandrocp mdex | 6ed94d905f97af188323f042698ae841c02293b4 | Vendor (CNA) |
| leandrocp mdex_native | 0.2.3 | Vendor (CNA) |
| leandrocp mdex_native | 947696c47bc22bea5dffc0f78c946fa6b70ce183 | Vendor (CNA) |
| Hex:mdex | 0.12.3 | Package registry (OSV) |
| Hex:mdex_native | 0.2.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Peter Ullrichfinder
- Leandro Pereiraremediation developer
- Jonatan Männchen / EEFanalyst
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.