Back to CVE records
High 8.8Published Oct 21, 2026

CVE-2026-114142toml-node: Prototype pollution: parsing a TOML document can write to Object.prototype

Updated under an hour ago ()

Does this affect you?

It affects BinaryMuse toml-node. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.40%, higher than 33% of scored CVEs.

toml-node is a TOML parser for Node.js and the browser. Prior to 5.0.1, toml.parse() can write attacker-controlled properties to Object.prototype because quoteDottedString() in lib/compiler.js produces the same bookkeeping string for distinct quoted key paths, allowing addTableArray() to clear another key's guard. The assign() path then descends through an unowned Date value without applying the owned-container check and can reach the prototype chain. Objects created elsewhere in the process can inherit the injected property. This issue is fixed in version 5.0.1.

CVSS
8.8 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-1321
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
0.40% (percentile 33)
Assigned by
GitHub_M
NVD analysis
Deferred
Record last updated
Oct 21, 2026
First seen by InfoSec Signals
Oct 21, 2026

Affected products

Affected products
BinaryMuse toml-node
binarymuse:toml_node (from the name)
before 5.0.1
CNA record

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.