CVE-2026-114144
toml-node is a TOML parser for Node.js and the browser. Prior to …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/BinaryMuse/toml-node/commit/9d52e384f6030932174d1afb0d910154dd62dead
- github.com/BinaryMuse/toml-node/releases/tag/v5.0.1
- github.com/BinaryMuse/toml-node/security/advisories/GHSA-9qmh-m7c6-f92p
- nvd.nist.gov/vuln/detail/CVE-2026-114144
- github.com/advisories/GHSA-9qmh-m7c6-f92p
- nvd.nist.gov/vuln/detail/CVE-2026-114144
- cve.org/CVERecord?id=CVE-2026-114144
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.