ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-114143

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

Published Oct 21, 2026 · catalog updated Oct 28, 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-114143. EPSS is 0.47%. 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
High8.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.47%
Remediation
Version ranges on file
Affected products
npm toml · package npm

## Summary is vulnerable to a quadratic-complexity (O(n²)) denial-of-service via a single long dotted key, table header, or inline-table key. A ~100KB crafted document causes a multi-second synchronous hang; a ~200KB document crashes the Node.js process outright with an uncatchable out-of-memory error. This is a separate, unpatched code path from the previously fixed stack-overflow DoS ( ) — it requires no array/inline-table nesting at all, and is confirmed unaffected by the option that fixed that earlier issue. ## Affected component / version - Package: (npm), repository - Functions: , , in - Confirmed present in the audited checkout at commit (2026-07-16), one commit past the tag (a changelog-only change) — i.e. present in , the latest release. Not exhaustively verified against every prior release, but the affected functions are unrelated to 's BigInt/Temporal changes (per ), so the defect likely predates that release as well. ## Details ( ) forwards the caller-supplied string to and then with no length or structural validation. Inside , three separate functions each walk a dotted key's segments in a loop and, on **every** iteration, recompute the full path-prefix string from scratch: - (lines 69-107, the sink at line 81): — reached for top-level dotted-key assignments like . - (lines 247-281, the sink at line 252): the identical pattern via — reached from table headers and array-of-tables via / . - (lines 184-202, the sink at line 187): the identical pattern — reached from inline-table dotted keys like . allocates a new array of length ; / (lines 311-317) then does , also O(i). Since this runs on every one of the segments of a dotted key, total work is , not . The string is computed unconditionally on the happy path (only ever *used* if an error is about to be thrown), so there is no early exit that makes this cheap in practice. No limit exists anywhere on dotted-key segment count: and in (lines 122, 311) are unbounded repetitions, parsed iteratively rather than

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-114143

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-114143. EPSS is 0.47%. 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-407. EPSS 0.47%. 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() repeatedly slices and rejoins every path prefix in lib/compiler.js while processing long dotted keys, table headers, array-of-tables headers, and inline-table keys in assign(), deepRef(), and setNestedKey(). The resulting quadratic work can block the Node.js event loop for several seconds, and sufficiently long pa

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ## Summary is vulnerable to a quadratic-complexity (O(n²)) denial-of-service via a single long dotted key, table header, or inline-table key. A ~100KB crafted document causes a multi-second synchronous hang; a ~200KB document crashes the Node.js process outright with an uncatchable out-of-memory error. This is a separate, unpatched code path from the previously fixed stack-overflow DoS ( ) — it re

  3. Oct 28, 2026 · NIST NVD

    Updated

    toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() repeatedly slices and rejoins every path prefix in lib/compiler.js while processing long dotted keys, table headers, array-of-tables headers, and inline-table keys in assign(), deepRef(), and setNestedKey(). The resulting quadratic work can block the Node.js event loop for several seconds, and sufficiently long pa

Sources

  • CVE.orgVulnerability recordCVE-2026-114143

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-114143

    30-day exploitation probability 0.47%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-9j65-hcg3-gc64

    toml-node: Quadratic-complexity DoS via long dotted keys or table paths in toml.parse()

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

    toml.parse() is vulnerable to a quadratic-complexity (O(n²)) denial-of-service via a single long dotted key, table header, or inline-table key. A ~100KB crafted document causes a multi-second synchronous hang; a ~200KB document crashes the Node.js process outright with an uncatchable out-of-memory error. This is a separate, unpatched code path from the previously fixed stack-overflow DoS (GHSA-82x

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

    toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() repeatedly slices and rejoins every path prefix in lib/compiler.js while processing long dotted keys, table headers, array-of-tables headers, and inline-table keys in assign(), deepRef(), and set

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

    Inefficient Algorithmic Complexity

    security.snyk.io
  • Tenable CVE DatabaseVulnerability recordCVE-2026-114143

    toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() repeatedly slices and rejoins every path prefix in lib/compiler.js while processing long dotted keys, table headers, array-of-tables headers, and inline-table keys in assign(), deepRef(), and setNestedKey(). The resulting quadratic work can block the Node.js event loop for several seconds, and sufficiently long pa

    tenable.com

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
  • Tenable CVE DatabaseOct 28, 2026
  • NIST NVDOct 28, 2026
  • Snyk Vulnerability DatabaseOct 24, 2026
  • GitHub Advisory DatabaseOct 23, 2026
  • GitLab Advisory DatabaseOct 23, 2026
  • CVE.orgOct 22, 2026