Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114143 Overview
CVE-2026-114143 is a denial-of-service vulnerability in toml-node, a TOML parser for Node.js and the browser. Versions prior to 5.0.1 perform quadratic work when processing long dotted keys, table headers, array-of-tables headers, and inline-table keys. The parser repeatedly slices and rejoins every path prefix inside lib/compiler.js through the assign(), deepRef(), and setNestedKey() functions. Attackers who can submit crafted TOML input block the Node.js event loop for several seconds. Sufficiently long key paths terminate the process through memory exhaustion. The maxDepth option does not count key segments and provides no mitigation. Maintainers fixed the issue in version 5.0.1.
Critical Impact
Remote, unauthenticated attackers can stall or crash Node.js services that parse untrusted TOML input, impacting application availability.
Affected Products
- toml-node versions prior to 5.0.1
- Node.js applications using toml.parse() on untrusted input
- Browser applications bundling vulnerable toml-node releases
Discovery Timeline
- 2026-10-21 - CVE-2026-114143 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114143
Vulnerability Analysis
The vulnerability is an algorithmic complexity flaw [CWE-407] in the key-path handling logic of lib/compiler.js. During parsing, the compiler walks each dotted key segment and reconstructs the full path prefix by slicing and rejoining the segment array on every step. Processing a dotted key with N segments triggers work that grows with N squared rather than linearly. For long paths, this behavior monopolizes the single-threaded Node.js event loop and blocks all other request handlers in the process. When paths grow further, intermediate string allocations consume available heap, driving the Node.js runtime into out-of-memory termination.
Root Cause
The root cause is inefficient prefix construction inside assign(), deepRef(), and setNestedKey(). These helpers rebuild the dotted path for each key segment instead of reusing a single accumulated reference, producing quadratic time and memory behavior. The existing maxDepth option limits nesting depth but does not cap the number of segments in a single dotted key or table header, so it does not bound the vulnerable loops.
Attack Vector
Exploitation requires only that an attacker supply TOML content to a vulnerable toml.parse() call. Any application that accepts TOML through HTTP uploads, configuration APIs, webhooks, or user-submitted artifacts is reachable over the network without authentication or user interaction. A single document containing a dotted key or table header with thousands of segments is sufficient to stall the event loop. Larger inputs escalate the condition to memory exhaustion and process termination. See the GitHub Security Advisory GHSA-9j65-hcg3-gc64 for the maintainer analysis.
Detection Methods for CVE-2026-114143
Indicators of Compromise
- Node.js processes showing sustained 100% CPU usage correlated with inbound TOML parsing requests.
- Out-of-memory crashes or JavaScript heap out of memory errors in services that consume TOML input.
- Request payloads containing abnormally long dotted keys or table headers, for example strings with hundreds or thousands of . characters.
Detection Strategies
- Inventory applications and dependencies for toml-node versions below 5.0.1 using Software Composition Analysis against package.json and package-lock.json.
- Add web application firewall or reverse-proxy rules that reject TOML uploads exceeding a reasonable segment or size threshold.
- Instrument toml.parse() call sites with event-loop lag metrics to flag parsing operations exceeding expected latency.
Monitoring Recommendations
- Alert on Node.js event-loop lag or request-latency spikes on endpoints that accept configuration or TOML content.
- Monitor container restart counts and OOMKilled events for workloads that process user-supplied documents.
- Correlate inbound HTTP payload size and structure with downstream parser performance to identify abuse patterns.
How to Mitigate CVE-2026-114143
Immediate Actions Required
- Upgrade toml-node to version 5.0.1 or later across all Node.js services and client bundles.
- Audit all toml.parse() call sites and reject untrusted TOML input until the dependency is patched.
- Enforce request size limits at the application and proxy layers for endpoints that accept TOML content.
Patch Information
The fix is included in toml-node5.0.1. The upstream fix is tracked in the GitHub commit 609c873 and published in the v5.0.1 release notes. Update package.json to require ^5.0.1 and regenerate the lockfile to ensure transitive dependencies also resolve the patched version.
Workarounds
- Restrict request body size on routes that accept TOML to a value well below the thresholds that trigger pathological parsing.
- Validate input structure before parsing by rejecting documents whose keys or headers exceed a conservative segment count.
- Offload TOML parsing to a short-lived worker thread or child process with strict memory and CPU limits to contain blast radius.
# Configuration example
npm install toml@^5.0.1
npm audit --production
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

