CVE-2026-114144

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

7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

0.4% chance of exploitation in the next 30 days; higher than 37% of CVEs (scores of 2026-10-25)

CWEs

CWE-400, CWE-770

Published

2026-10-21

Modified

2026-10-22

Record from

the NVD, synced 2026-10-23

Packages (OSV)

References

• https://github.com/BinaryMuse/toml-node/commit/9d52e384f6030932174d1afb0d910154dd62dead
• https://github.com/BinaryMuse/toml-node/releases/tag/v5.0.1
• https://github.com/BinaryMuse/toml-node/security/advisories/GHSA-9qmh-m7c6-f92p

Check your stackJSON