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


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-9qmh-m7c6-f92p, ROOT-APP-NPM-CVE-2026-114144

## What is CVE-2026-114144?

CVE-2026-114144 is a high-severity vulnerability in BinaryMuse toml-node, published on 21 Oct 2026. 

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

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-114144?

2 open source packages ship an affected version, including toml.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `toml` | npm | All versions | 5.0.1 |
| `toml` | npm | All versions | 5.0.1 |

## How do I fix CVE-2026-114144?

Upgrade toml to 5.0.1 or later.

## Is CVE-2026-114144 being exploited?

There is no known exploitation of CVE-2026-114144 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114144 and fix it if it is affected.

What it is: CVE-2026-114144 is a high-severity vulnerability in BinaryMuse toml-node, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114144 in the wild and no public exploit code.

Affected packages and fixed versions:
- toml (npm): affected all versions; fixed in 5.0.1
- toml (npm): affected all versions; fixed in 5.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114144/ (Markdown: https://insights.sbomify.com/CVE-2026-114144/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114144
- OSV: https://osv.dev/vulnerability/CVE-2026-114144

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114144/
Summaries are generated and may contain mistakes; the official description above is the record.