CVE-2026-114143: high-severity vulnerability in BinaryMuse toml-node
toml-node: Quadratic-complexity DoS via long dotted keys or table paths in toml.parse()
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.5%
toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() repeatedly slices and rejoins every path prefix in lib/compiler.js while processing long dotted keys, table headers, array-of-tables headers, and inline-table keys in assign(), deepRef(), and setNestedKey(). The resulting quadratic work can block the Node.js event loop for several seconds, and sufficiently long paths can terminate the process through memory exhaustion. The maxDepth option does not limit key-segment count and therefore does not mitigate this path. This issue is fixed in version 5.0.1.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Affected products
BinaryMuse · toml-nodeRelated CVEs — BinaryMuse toml-node
In the same product, most dangerous first.
CVE-2026-63376HIGHtoml-node: Prototype Pollution Leads to `Object.prototype` Corruption via `__proto__` Key-Path DesynchronizationEPSS 0.7%CVE-2026-77465HIGHtoml-node: Uncontrolled RecursionEPSS 0.6%CVE-2026-114142HIGHtoml-node: Prototype pollution: parsing a TOML document can write to Object.prototypeEPSS 0.5%CVE-2026-114141HIGHtoml-node: Quadratic-complexity DoS via many array-of-tables headers in toml.parse()EPSS 0.5%CVE-2026-114144HIGHtoml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()EPSS 0.4%