Recommended action window: Monitor and triage in normal cycle
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
‼️ A 4-line TOML file can write to Object.prototype and reach every object in your process. CVE-2026-114142 toml.parse() through 5.0.0: a colliding key path clears a guard, then a Date leads into Object.prototype. Fixed in 5.0.1. Parsing untrusted TOML? https://github.com/advisories/GHSA-h895-cgqg-jf52