Quick answers
- Is CVE-2026-114144 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114144 being exploited in the wild.
- How severe is CVE-2026-114144?
- High severity, with a CVSS score of 7.5, published 21 October 2026.
- Which products and versions are affected?
- BinaryMuse Toml-Node before 5.0.1; toml (npm) <= 5.0.0, SEMVER:introduced=0,fixed=5.0.1.
- Is there a fix for CVE-2026-114144?
- Yes. toml (npm): upgrade to 5.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114144 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114144?
- Check whether you run BinaryMuse Toml-Node or toml (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- toml (npm): upgrade to 5.0.1 or later
npm install toml@5.0.1
Technical details
The vulnerability exists in toml.parse(), which passes unbounded digit sequences to JavaScript's BigInt() function before validating whether the resulting value fits TOML's 64-bit integer range. Converting sufficiently long integer strings takes super-linear CPU time and blocks the Node.js event loop synchronously. An attacker with the ability to supply TOML input can trigger a denial of service by crafting a document with multi-megabyte integer literals.
Affected products
- BinaryMuse toml-node before 5.0.1
Identifiers
- CVE-2026-114144
- GHSA-9qmh-m7c6-f92p
Timeline
- 2026-10-21: disclosed