CVE-2026-63376: high-severity vulnerability in BinaryMuse toml-node
toml-node: Prototype Pollution Leads to `Object.prototype` Corruption via `__proto__` Key-Path Desynchronization
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.2epss 0.7%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Affected products
BinaryMuse · toml-nodeRelated CVEs — BinaryMuse toml-node
In the same product, most dangerous first.
CVE-2026-77465HIGHtoml-node: Uncontrolled RecursionEPSS 0.6%CVE-2026-114142HIGHtoml-node: Prototype pollution: parsing a TOML document can write to Object.prototypeEPSS 0.5%CVE-2026-114143HIGHtoml-node: Quadratic-complexity DoS via long dotted keys or table paths in toml.parse()EPSS 0.5%CVE-2026-114141HIGHtoml-node: Quadratic-complexity DoS via many array-of-tables headers in toml.parse()EPSS 0.5%CVE-2026-114144HIGHtoml-node: Uncontrolled resource consumption (CPU DoS) via unbounded-length integer literals in toml.parse()EPSS 0.4%