CVE-2026-63376: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in BinaryMuse toml-node
Description
toml-node is a TOML parser for Node.js and the browser. Prior to 4.1.2, toml.parse() in lib/compiler.js can be tricked by a table path such as a.b.y.__proto__.__proto__, allowing traversal from a scalar value into Number.prototype and Object.prototype. The currentPath tracking value uses both arrays and strings, so valueAssignments records a comma-joined path such as a,b.y while deepRef checks the dot-joined path a.b.y, allowing the duplicate-key guard to miss and attacker-controlled keys to be written to Object.prototype. A table-array prefix-clearing path in addTableArray can also erase guard state before the same __proto__ traversal. Injected properties become visible throughout the Node.js process and can cause denial of service, logic or authorization bypass, or code execution when an application contains a suitable gadget. This issue is fixed in version 4.1.2.
CVSS v3.1
Score 8.2high
Affected software
BinaryMuse
toml-node
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in toml-node's parsing logic where the currentPath tracking uses inconsistent formats (arrays and strings) leading to a duplicate-key guard bypass. An attacker can craft table paths such as a.b.y.__proto__.__proto__ to traverse and modify Number.prototype and Object.prototype. Additionally, a table-array prefix-clearing path can erase guard state, allowing prototype pollution. Injected properties affect the entire Node.js process, enabling various impacts including denial of service and potential code execution. The vulnerability is addressed in toml-node version 4.1.2.
Potential Impact
Exploitation of this vulnerability allows an attacker to inject or modify properties on Object.prototype, which can lead to denial of service, logic or authorization bypass, or arbitrary code execution if the application uses vulnerable gadgets. The impact is limited to applications using vulnerable versions of toml-node prior to 4.1.2.
Mitigation Recommendations
A fix is available in toml-node version 4.1.2. Users should upgrade to version 4.1.2 or later to remediate this vulnerability. No other mitigation guidance is provided by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-16T17:39:30.170Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a99de23acd9273b497230c1
Added to database: 09/03/2026, 20:52:51 UTC
Last enriched: 09/07/2026, 11:27:58 UTC
Last updated: 10/18/2026, 06:48:18 UTC
Views: 102
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.