Unbounded native memory leak in mdex escaped-tag rendering enables unauthenticated denial of service
Missing Release of Memory after Effective Lifetime vulnerability in leandrocp mdex and mdex_native allows an attacker who controls a rendered document to cause a denial of service through unbounded native memory exhaustion. The native rendering code permanently leaks memory when rendering a document that contains escaped-tag nodes. The conversion of each %MDEx.EscapedTag{} node into its native representation (From for NodeValue in the Rust NIF) calls Box::leak on the caller-supplied literal string, which surrenders the backing allocation so that it lives for the entire lifetime of the operating system process and is never freed. Both the byte length of each literal and the number of escaped-tag nodes in a document are attacker-controlled, and there is no size cap, rate limit, or string interning on this path. Every render of a document containing escaped-tag nodes therefore leaks literal_size x node_count bytes that can never be reclaimed, and repeated renders accumulate without bound. Rendering reaches this path through the public MDEx.to_html/1 entry point and any other API that renders a supplied %MDEx.Document{}. Any application that uses mdex (or mdex_native directly) to render documents derived from user-supplied content is affected. Because the leaked memory is never reclaimed for the life of the BEAM process, an attacker can drive resident memory upward without limit until the node exhausts memory and crashes, taking down every process on it. The vulnerable native cod
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-53429
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 16:39 UTC · Revision 1
Source evidence
Unbounded native memory leak in mdex escaped-tag rendering enables unauthenticated denial of service
core-osv · Original sourcePublished 29 Jun 2026, 19:07 UTC
Missing Release of Memory after Effective Lifetime vulnerability in leandrocp mdex and mdex_native allows an attacker who controls a rendered document to cause a denial of service through unbounded native memory exhaustion. The native rendering code permanently leaks memory when rendering a document that contains escaped-tag nodes. The conversion of each %MDEx.EscapedTag{} node into its native representation (From for NodeValue in the Rust NIF) calls Box::leak on the caller-supplied literal string, which surrenders the backing allocation so that it lives for the entire lifetime of the operating system process and is never freed. Both the byte length of each literal and the number of escaped-tag nodes in a document are attacker-controlled, and there is no size cap, rate limit, or string interning on this path. Every render of a document containing escaped-tag nodes therefore leaks literal_size x node_count bytes that can never be reclaimed, and repeated renders accumulate without bound. Rendering reaches this path through the public MDEx.to_html/1 entry point and any other API that renders a supplied %MDEx.Document{}. Any application that uses mdex (or mdex_native directly) to render documents derived from user-supplied content is affected. Because the leaked memory is never reclaimed for the life of the BEAM process, an attacker can drive resident memory upward without limit until the node exhausts memory and crashes, taking down every process on it. The vulnerable native cod
osv:CVE-2026-53429
Complete source record
{
"id": "2a29d7bcf5d413183d23670c1d9e6d6881ef5d52fa74a31607a480d0b24e2d81",
"url": "https://osv.dev/vulnerability/CVE-2026-53429",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Unbounded native memory leak in mdex escaped-tag rendering enables unauthenticated denial of service",
"summary": "Missing Release of Memory after Effective Lifetime vulnerability in leandrocp mdex and mdex_native allows an attacker who controls a rendered document to cause a denial of service through unbounded native memory exhaustion. The native rendering code permanently leaks memory when rendering a document that contains escaped-tag nodes. The conversion of each %MDEx.EscapedTag{} node into its native representation (From for NodeValue in the Rust NIF) calls Box::leak on the caller-supplied literal string, which surrenders the backing allocation so that it lives for the entire lifetime of the operating system process and is never freed. Both the byte length of each literal and the number of escaped-tag nodes in a document are attacker-controlled, and there is no size cap, rate limit, or string interning on this path. Every render of a document containing escaped-tag nodes therefore leaks literal_size x node_count bytes that can never be reclaimed, and repeated renders accumulate without bound. Rendering reaches this path through the public MDEx.to_html/1 entry point and any other API that renders a supplied %MDEx.Document{}. Any application that uses mdex (or mdex_native directly) to render documents derived from user-supplied content is affected. Because the leaked memory is never reclaimed for the life of the BEAM process, an attacker can drive resident memory upward without limit until the node exhausts memory and crashes, taking down every process on it. The vulnerable native cod",
"evidence": "osv:CVE-2026-53429",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-53429",
"aliases": [
"CVE-2026-53429",
"EEF-CVE-2026-53429",
"GHSA-cmvp-gp9f-23xw"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/leandrocp/mdex",
"type": "GIT",
"events": [
{
"introduced": "81e4d14dd3aa5b206e395c7f372b9b413793015f"
},
{
"fixed": "6ed94d905f97af188323f042698ae841c02293b4"
},
{
"introduced": "711877566dced6aa7a98a0609cf6c5cbc8971644"
},
{
"fixed": "2cb9eb2f6014414b40c8f1e5d5181b9692626c38"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "81e4d14dd3aa5b206e395c7f372b9b413793015f"
},
{
"fixed": "6ed94d905f97af188323f042698ae841c02293b4"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "0.11.0"
},
{
"fixed": "0.12.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
},
{
"repo": "https://github.com/leandrocp/mdex_native",
"type": "GIT",
"events": [
{
"introduced": "956528c5e31746253347029e810a969ab916fd27"
},
{
"fixed": "cbd927fb5061b488de8d90a8ef6df65718ca1fe6"
},
{
"introduced": "0"
},
{
"fixed": "b6caf84e9dd035654ed7e8955086ab37afdaa7a0"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "956528c5e31746253347029e810a969ab916fd27"
},
{
"fixed": "cbd927fb5061b488de8d90a8ef6df65718ca1fe6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "0.1.0"
},
{
"fixed": "0.2.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "cbd927fb5061b488de8d90a8ef6df65718ca1fe6"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v0.12.2",
"v0.12.1",
"v0.12.0",
"v0.11.7",
"v0.11.6",
"v0.11.5",
"v0.11.4",
"v0.11.3",
"v0.11.2",
"v0.11.1",
"v0.2.2",
"v0.2.1",
"v0.2.0",
"v0.1.5",
"v0.1.4",
"v0.1.3",
"v0.1.2",
"v0.1.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53429.json"
}
}
],
"modified": "2026-10-28T02:30:20.828980801Z",
"provider": "osv",
"references": [
"https://cna.erlef.org/cves/CVE-2026-53429.html",
"https://github.com",
"https://osv.dev/vulnerability/EEF-CVE-2026-53429",
"https://repo.hex.pm",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53429.json",
"https://github.com/leandrocp/mdex_native/security/advisories/GHSA-cmvp-gp9f-23xw",
"https://nvd.nist.gov/vuln/detail/CVE-2026-53429",
"https://github.com/leandrocp/mdex_native/commit/cbd927fb5061b488de8d90a8ef6df65718ca1fe6",
"https://github.com/leandrocp/mdex",
"https://github.com/leandrocp/mdex_native"
],
"provider_metadata": {
"cwe_ids": [
"CWE-401"
],
"cna_assigner": "EEF",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53429.json"
}
},
"related_cves": [
{
"value": "CVE-2026-53429",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 487275,
"published_at": "2026-06-29T19:07:16.954+00:00"
}