<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>BinaryMuse - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/binarymuse/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 29 Oct 2026 12:31:24 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/binarymuse/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>BinaryMuse toml-node: Quadratic-complexity denial-of-service (CVE-2026-114143)</title><link>https://feed.craftedsignal.io/briefs/2026-10-toml-node-dos-218678a9/</link><pubDate>Thu, 29 Oct 2026 12:31:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-toml-node-dos-218678a9/</guid><description>The toml-node library is vulnerable to a quadratic-complexity denial-of-service attack, where long dotted keys in TOML documents cause CPU exhaustion or process crashes via memory depletion.</description><content:encoded><![CDATA[<p>The <code>toml-node</code> library (npm package <code>toml</code>) is vulnerable to a quadratic-complexity (O(n²)) denial-of-service (DoS) via long dotted keys, table headers, or inline-table keys. The library repeatedly recomputes the full path-prefix string during parsing, with no limits on segment count or total input length. This vulnerability is not mitigated by the existing <code>maxDepth</code> option and affects <code>assign()</code>, <code>deepRef()</code>, and <code>setNestedKey()</code> functions.</p>
<h2 id="impact">Impact</h2>
<ul>
<li><strong>Event Loop Blocking:</strong> A ~100KB payload induces a multi-second synchronous hang, stalling the entire Node.js event loop.</li>
<li><strong>Process Crash:</strong> A ~200KB payload causes a fatal <code>JavaScript heap out of memory</code> error, terminating the Node.js process.</li>
<li><strong>Unauthenticated Access:</strong> Exploitation requires only that the target application parses a user-controlled TOML input (e.g., config uploads or API request bodies).</li>
</ul>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade or apply patches to <code>toml-node</code> as they become available.</li>
<li>If a patch is unavailable, implement a pre-parsing input size limit (e.g., rejecting TOML documents exceeding a reasonable size such as 10KB) to prevent the O(n²) trigger.</li>
<li>Implement length validation on key segments for any TOML data processed by the library.</li>
<li>Migrate away from <code>toml-node</code> if the library is not actively maintained to address these structural vulnerabilities.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>denial-of-service</category><category>vulnerability</category><category>javascript</category><category>nodejs</category><category>supply-chain</category></item></channel></rss>