cve.bz

CVE-2026-114142 binarymuse toml-node: Prototype Pollution

8.8 highEPSS 0.5%Fix available

High (8.8) in binarymuse toml-node. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in toml 5.0.1.

On this page
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.

Severity

CVSS 4.0

8.8 high
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
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • toml (npm): fixed in 5.0.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-114142 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114142?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114142?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114142 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
BinaryMuse toml-node< 5.0.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h895-cgqg-jf52npmtoml<5.0.15.0.1

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON