Vulnerability · Published Oct 21, 2026 · Assigned by GitHub_M
CVE-2026-114144toml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()
High 7.5
In plain English
A high-severity uncontrolled resource consumption in toml-node from BinaryMuse. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 38% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | toml | 5.0.1 | GHSA-9qmh-m7c6-f92p |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| BinaryMuse | toml-node | < 5.0.1 |
Weakness: CWE-400, CWE-770 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H