# CVE-2026-53428: Unbounded memory allocation in highlight_lines range expansion in mdex > An unauthenticated attacker can cause a denial of service by supplying Markdown with a large highlight_lines range, triggering excessive memory allocation. - **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Jun 2026 - **Updated:** 30 Jun 2026 - **Also known as:** EEF-CVE-2026-53428, GHSA-j93q-9cvj-rxfm ## What is CVE-2026-53428? CVE-2026-53428 is a medium-severity denial of service vulnerability in leandrocp mdex, published on 29 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Memory Allocation with Excessive Size Value vulnerability in leandrocp mdex allows an unauthenticated attacker to cause a denial of service through unbounded memory allocation. comrak_nif::lumis_adapter::LumisAdapter::parse_highlight_lines in native/comrak_nif/src/lumis_adapter.rs eagerly expands a user-controlled inclusive line range from a fenced code block's highlight_lines decorator into a Vec, pushing one element per integer in the range with no upper bound on the range size. An attacker who can supply Markdown that an application renders with MDEx.to_html/2 (for example a comment, chat message, or wiki page) can embed a code block whose info string is rust highlight_lines="1-100000000", forcing the native adapter to allocate roughly 8 bytes per line in the range. A payload that differs by only a few bytes can therefore allocate hundreds of megabytes, and a sufficiently large range (for example 1-2000000000) exhausts host memory and aborts the BEAM, denying service to every user of the rendering process. The per-line write loop additionally tests membership with a linear scan over the same vector, degrading rendering to a quadratic cost even for ranges that do not immediately exhaust memory. The vulnerable native code originally shipped inside mdex (in native/comrak_nif/src/lumis_adapter.rs) and was later extracted into the separate mdex_native package (native/mdex_native_nif/src/lumis_adapter.rs), where it remains unpatched. This issue affects mdex from 0.11.0 before 0.12.3, and mdex_native from 0.1.0 before 0.2.3. Weakness: CWE-789 (Memory Allocation with Excessive Size Value) ## Which versions are affected by CVE-2026-53428? 2 open source packages ship an affected version, including mdex and mdex_native. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mdex` | Hex | From 0.11.0 | 0.12.3 | | `mdex_native` | Hex | From 0.1.0 | 0.2.3 | ## How do I fix CVE-2026-53428? Upgrade mdex to 0.12.3 or later. ## Is CVE-2026-53428 being exploited? There is no known exploitation of CVE-2026-53428 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-53428 and fix it if it is affected. What it is: CVE-2026-53428 is a medium-severity denial of service vulnerability in leandrocp mdex, published on 29 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-53428 in the wild and no public exploit code. Affected packages and fixed versions: - mdex (Hex): affected from 0.11.0; fixed in 0.12.3 - mdex_native (Hex): affected from 0.1.0; fixed in 0.2.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-53428/ (Markdown: https://insights.sbomify.com/CVE-2026-53428/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53428 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53428 - OSV: https://osv.dev/vulnerability/CVE-2026-53428 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-53428/ Summaries are generated and may contain mistakes; the official description above is the record.