ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-114141

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 8, 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-114141. 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 many array-of-tables ( ) headers. in rescans two entire bookkeeping Sets on every header without pruning unrelated or distinct entries, so a document containing n such headers costs O(n²) compiler work. A ~321KB document of 20,000 distinct-named blocks takes ~10.3 seconds to parse — a completely ordinary-looking TOML shape (a flat settings block plus one or more array-of-tables sections), not a contrived edge case. This is a separate, unpatched code path from the previously fixed stack-overflow DoS ( ) and requires no key nesting or dotted keys at all. ## Affected component / version - Package: (npm), repository - Function: 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 function is 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. Every (array-of-tables) header is routed ( , ) to ( ), which performs two full linear scans on every call: ( ) and accumulate one entry per top-level key/table/array path ever assigned in the entire document. Each scan prunes only entries matching the *currently reopened* path via ( : ); anything else — an unrelated top-level key, or simply a *different* array-of-tables name — is never removed and is rescanned in full on every subsequent header for the rest of the parse. has no early exit, so this is unconditionally O(current Set size) on every call, giving O(n²) total work for n such headers. ## Proof of Concept The sharpest reproduction needs no unrelated keys at all — just N array-of-tables headers with N *distinct* names, since nothing is ever pruned when no name repeats: Measured timings (Node, direct execution against th

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

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-114141. 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, the toml.parse() compiler's addTableArray() function in lib/compiler.js rescans the complete assignedPaths and valueAssignments bookkeeping sets for every array-of-tables header. Distinct [[name]] paths are not pruned, so a document with many such headers causes quadratic synchronous work and can block the Node.js event loop,

  2. Oct 22, 2026 · GitHub Advisory Database

    Updated

    ## Summary is vulnerable to a quadratic-complexity (O(n²)) denial-of-service via many array-of-tables ( ) headers. in rescans two entire bookkeeping Sets on every header without pruning unrelated or distinct entries, so a document containing n such headers costs O(n²) compiler work. A ~321KB document of 20,000 distinct-named blocks takes ~10.3 seconds to parse — a completely ordinary-looking TOML

Sources

  • CVE.orgVulnerability recordCVE-2026-114141

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-114141

    30-day exploitation probability 0.47%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-4qx8-w7c3-pj3p

    toml-node: Quadratic-complexity DoS via many array-of-tables headers in toml.parse()

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

    toml.parse() is vulnerable to a quadratic-complexity (O(n²)) denial-of-service via many array-of-tables ([[name]]) headers. addTableArray() in lib/compiler.js rescans two entire bookkeeping Sets on every [[name]] header without pruning unrelated or distinct entries, so a document containing n such headers costs O(n²) compiler work. A ~321KB document of 20,000 distinct-named [[name]] blocks takes ~

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

    toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, the toml.parse() compiler's addTableArray() function in lib/compiler.js rescans the complete assignedPaths and valueAssignments bookkeeping sets for every array-of-tables header. Distinct [[name]] paths are n

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

    Inefficient Algorithmic Complexity

    security.snyk.io

References

Freshness

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

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