CVE-2026-114144 · GHSA-9qmh-m7c6-f92p

toml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()

Risk score: 60/100
CVSS: 7.5 v3.1
Exploit chance (30 days): 0.3%
Published: 21 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is: 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 suff…
Affected: toml (npm) <= 5.0.0
Fix: Upgrade toml to 5.0.1 or later.
Exploitation: No known exploitation

Why it is Amber

CVSS 7.5 high
Remotely exploitable without logging in
On your watchlist: npm

Affected packages

Package	Ecosystem	Vulnerable	Fixed in
toml	npm	<= 5.0.0	5.0.1

References

Original 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.

Last activity 21 Oct 2026. Patch Forecast updates every hour.