Read the docs

CPU denial of service in toml-node via long integer literals

Priority HIGH 72CWE-400Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-400.

Summary

toml-node versions before 5.0.1 are affected, and so is the npm package toml from 0 before 5.0.1. The parser passes unbounded integer digit sequences to BigInt() before checking the 64-bit range, which is CWE-400. An attacker who supplies one crafted TOML document can block the Node.js event loop and deny service to concurrent work in the process.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.0044 38th percentileScored 2026-11-08
Fix Partial toml-node (BinaryMuse): 5.0.1toml (npm): 5.0.1Red Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
BinaryMusetoml-nodebefore 5.0.15.0.1Patch availableCNA
—toml (npm)before 5.0.15.0.1Patch availableGHSA-9qmh-m7c6-f92p
  • toml-node VendorBinaryMuse Affected before 5.0.1 Fixed in 5.0.1 Patch available CNA
  • toml (npm) Vendor— Affected before 5.0.1 Fixed in 5.0.1 Patch available GHSA-9qmh-m7c6-f92p

Remediation

Upgrade toml-node to 5.0.1, the fixed version named in the source description, and upgrade the npm package toml to 5.0.1. Red Hat lists Red Hat Enterprise Linux 10 as affected with no fix available.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

  • Fix · CNA toml-node (BinaryMuse) Fixed in 5.0.1
  • Fix · GHSA-9qmh-m7c6-f92p toml (npm) Fixed in 5.0.1 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-114144
  2. 2026-10-22 Affected versions changed · Red Hat
  3. 2026-10-22 CVSS score added · Red Hat
  4. 2026-10-22 Alias added: GHSA-9qmh-m7c6-f92p
  5. 2026-10-22 Fix available: npm/[email protected] · GHSA-9qmh-m7c6-f92p
  6. 2026-10-22 CVSS score added · GHSA-9qmh-m7c6-f92p
  7. 2026-10-22 Weakness changed · GHSA-9qmh-m7c6-f92p
  8. 2026-10-22 5 new references · GHSA-9qmh-m7c6-f92p
  9. 2026-10-23 Priority changed: MEDIUM → LOW
  10. 2026-10-30 CISA SSVC decision points changed
  11. 2026-10-30 Priority changed: LOW → HIGH

References

  • TI-2026-78987 Quadratic complexity denial of service in toml-node TOML parser CVSS 4.0HIGH 8.7
  • TI-2026-45178 toml-node: Prototype Pollution Leads to `Object.prototype` Corruption via `__proto__` Key-Path Desynchronization CVSS 3.1HIGH 8.2
  • TI-2026-78986 Prototype pollution in toml-node parser writes to Object.prototype CVSS 4.0HIGH 8.8
  • TI-2026-78985 Quadratic complexity in toml-node allows denial of service CVSS 4.0HIGH 8.7
  • TI-2026-54014 toml-node: Uncontrolled Recursion CVSS 3.1HIGH 7.5

Sources