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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-114144: 0.44% estimated exploitation activity in the next 30 days; percentile 38.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary toml.parse() converts integer literals (hex, octal, binary, and decimal) to BigInt without first bounding the length of the digit sequence. Since BigInt(string) construction from a very long numeric string runs in super-linear time, a single small, well-formed TOML document containing one long integer literal can pin a Node.js process's event loop at 100% CPU for several seconds — a denial of service for any application that parses attacker-supplied or third-party TOML. No authentication or complex crafting is required. Details In lib/parser.js, the grammar actions that build integer nodes call BigInt() directly on the matched digit text, with no upper bound on its length: - lib/parser.js:326 — hex: BigInt('0x' + stripUnderscores(digits)) - lib/parser.js:327 — octal: BigInt('0o' + stripUnderscores(digits)) - lib/parser.js:328 — binary: BigInt('0b' + stripUnderscores(digits)) - lib/parser.js:329 — decimal: BigInt(stripUnderscores(text)) The parser does enforce a nesting-depth…

Published by the source

22 Oct 2026, 16:36 UTC

Last modified by the source

22 Oct 2026, 16:45 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9qmh-m7c6-f92p

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-9qmh-m7c6-f92p

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-9qmh-m7c6-f92p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114144

Advisory: toml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()
IDs: CVE-2026-114144, GHSA-9qmh-m7c6-f92p
Record: https://patchnext.com/advisories/cve-2026-114144 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: toml 5.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm toml: affected <= 5.0.0; fixed in 5.0.1

## Suggested inspection (read-only)
- `npm ls toml --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on toml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9qmh-m7c6-f92p (GitHub-reviewed advisory GHSA-9qmh-m7c6-f92p lists affected ranges: npm toml >=0 <=5.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-9qmh-m7c6-f92p (OSV record GHSA-9qmh-m7c6-f92p lists affected ranges: npm toml >=0 <5.0.1 (fixed))

Commands are suggestions: review each one before running it.