ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-114144

toml-node is a TOML parser for Node.js and the browser.

Published Oct 21, 2026 · catalog updated Oct 22, 2026 · toml-node is a TOML

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-114144. EPSS is 0.44%. Act only if a listed version of toml-node is a TOML is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (toml-node is a TOML).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.44%
Remediation
Version ranges on file
Affected products
npm toml · package npm

### Summary converts integer literals (hex, octal, binary, and decimal) to without first bounding the length of the digit sequence. Since 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 , the grammar actions that build integer nodes call directly on the matched digit text, with no upper bound on its length: - — hex: - — octal: - — binary: - — decimal: The parser does enforce a nesting-depth limit ( , default 500, ) to guard against stack overflow from deeply nested arrays/inline tables (per GHSA-82x6-q7mm-w9cf). However, that guard only bounds *structural nesting* — it does not bound the length of a single scalar token. The subsequent 64-bit range check in ( , lines 143–150, comparing against / defined at lines 3–4) happens **after** the expensive conversion has already completed. It therefore provides no protection against this cost — the CPU time is already spent by the time the value is rejected as out of range. ### PoC **Measured results:** | Digits (hex) | Approx. payload size | Parse time | |---:|---:|---:| | 200,000 | ~200 KB | 141 ms | | 400,000 | ~400 KB | 276 ms | | 800,000 | ~800 KB | 685 ms | | 1,600,000 | ~1.6 MB | 1,761 ms | | 5,000,000 | ~5 MB | 6,061 ms | Growth is clearly super-linear. The same behavior reproduces for plain decimal literals (3,000,000 digits → ~6.3 s). ### Impact Any application that calls on untrusted or third-party input — config upload endpoints, CI/CD tools ingesting user-supplied files, package managers, linters, editors/language servers — is exposed. During the conversion, the event loop is fully blocked. In a typical single-threaded Node.js server this stalls **all** concurrent request handling, not

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm toml<= 5.0.0
  • package npmversion unspecified

How to fix CVE-2026-114144

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-114144. EPSS is 0.44%. Act only if a listed version of toml-node is a TOML is installed.

Which versions are affected?

Compare what you have installed with <= 5.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption; CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.44%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 21, 2026 · NIST NVD

    Detected

    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 blo

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ### Summary converts integer literals (hex, octal, binary, and decimal) to without first bounding the length of the digit sequence. Since 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

Sources

  • CVE.orgVulnerability recordCVE-2026-114144

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-114144

    30-day exploitation probability 0.44%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-9qmh-m7c6-f92p

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

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-114144

    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 serv

    advisories.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-114144

    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

    nvd.nist.gov
  • Snyk Vulnerability DatabasePackage advisorySNYK-JS-TOML-21431466

    Allocation of Resources Without Limits or Throttling

    security.snyk.io

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 6, 2026
  • Snyk Vulnerability DatabaseOct 25, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • GitLab Advisory DatabaseOct 23, 2026
  • CVE.orgOct 22, 2026
  • NIST NVDOct 22, 2026