CVE-2026-77465: CWE-674: Uncontrolled Recursion in BinaryMuse toml-node
Description
toml-node is a TOML parser for Node.js and the browser. Prior to 4.2.0, toml.parse() uses a Peggy 5.1.0 generated recursive-descent parser in lib/parser.js whose peg$parsevalue, peg$parsearray, and peg$parseinline_table_entry functions recurse through nested arrays and inline tables without a depth limit. A remote unauthenticated application parsing an attacker-controlled TOML document containing a few thousand nested arrays or inline tables can exhaust the Node.js call stack, raise an unexpected RangeError rather than the parser's SyntaxError, and terminate an unprotected request worker or process. The corresponding grammar source is src/toml.pegjs, where the generated parser must be bounded. This issue is fixed in version 4.2.0.
CVSS v3.1
Score 7.5high
Affected software
BinaryMuse
toml-node
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The toml-node package for Node.js and browsers uses a recursive-descent parser generated by Peggy 5.1.0. Prior to version 4.2.0, the parser's functions peg$parsevalue, peg$parsearray, and peg$parseinline_table_entry recurse through nested arrays and inline tables without any depth limit. This uncontrolled recursion allows a remote unauthenticated attacker to supply a TOML document with thousands of nested arrays or inline tables, exhausting the Node.js call stack and causing a RangeError. This error terminates the parsing process unexpectedly, potentially causing denial of service by crashing unprotected request workers or processes. The vulnerability is tracked as CVE-2026-77465 and is classified under CWE-674 (Uncontrolled Recursion). The fix involves bounding the recursion depth in the parser, implemented in toml-node version 4.2.0.
Potential Impact
An attacker can cause a denial of service by sending a specially crafted TOML document with deeply nested arrays or inline tables to an application using toml-node versions before 4.2.0. This triggers uncontrolled recursion in the parser, exhausting the call stack and causing the process or request worker to terminate unexpectedly. There is no impact on confidentiality or integrity, but availability is affected due to process termination.
Mitigation Recommendations
Upgrade toml-node to version 4.2.0 or later, where the recursion depth is properly bounded in the parser. No other mitigations are specified. Patch status is not explicitly confirmed in the vendor advisory, but the fix is stated to be in version 4.2.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T20:07:49.962Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a99de23acd9273b497230c3
Added to database: 09/03/2026, 20:52:51 UTC
Last enriched: 09/07/2026, 12:22:56 UTC
Last updated: 10/18/2026, 06:48:20 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.