CVE-2026-114144: high-severity vulnerability in BinaryMuse toml-node
toml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals 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 7.5epss 0.4%
toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() passes unbounded hexadecimal, octal, binary, and decimal digit sequences from lib/parser.js to BigInt() before reduceInteger() in lib/compiler.js checks whether the resulting value fits the TOML 64-bit integer range. Converting a sufficiently long integer string consumes super-linear CPU time and synchronously blocks the Node.js event loop, allowing one attacker-supplied TOML document to deny service to concurrent work in the process. The later range check cannot prevent the conversion cost because it executes after BigInt(). This issue is fixed in version 5.0.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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-114143HIGHtoml-node: Quadratic-complexity DoS via long dotted keys or table paths in toml.parse()EPSS 0.5%CVE-2026-114141HIGHtoml-node: Quadratic-complexity DoS via many array-of-tables headers in toml.parse()EPSS 0.5%