{"id":"EUVD-2026-58791","enisaUuid":"7b2e4727-de7a-32cd-bf2b-50300ff446b6","description":"js-toml is a TOML parser for JavaScript, Prior to version 1.1.2, the interpreter checks whether a key already exists in a parser-built container with `if (object[key])` instead of `if (key in object)`. When the prior value is a falsy primitive — `false`, `0`, `0n`, `0.0`, `-0`, or `\"\"` — the duplicate-key branch is skipped and the value is silently overwritten by a later sub-table, dotted-key sub-table, or array-of-tables sharing the same name. Per the TOML 1.0.0 spec (\"Defining a key multiple times is invalid\"; \"You cannot define any key or table more than once\"), this should be a parse error. The result is structural type confusion of attacker-named keys in the value returned by `load()`. A boolean-typed `false` (or numeric `0`) becomes a truthy object. Host applications that gate behavior on `if (config.flag)`, `if (!user.banned)`, `if (config.allowDelete)`, or `if (config.publicMode)` will silently take the truthy branch. This is distinct from GHSA-65fc-cr5f-v7r2 (the 1.0.2 prototype-pollution fix). `Object.prototype` is not polluted. The `Object.create(null)` mitigation from 1.0.2 is intact; the bug here is in the duplicate-key state machine, not in container construction. Version 1.1.2 patches the incorrect comparison.","datePublished":"Aug 14, 2026, 7:08:54 PM","dateUpdated":"Aug 17, 2026, 7:34:15 PM","baseScore":5.3,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","references":"https://github.com/sunnyadn/js-toml/security/advisories/GHSA-m34p-749j-x6m6\nhttps://github.com/sunnyadn/js-toml/commit/e0504fa5d3dcde2d1d588c9001c24b7b700beeeb\nhttps://github.com/sunnyadn/js-toml/releases/tag/v1.1.2\n","aliases":"CVE-2026-50029\nGHSA-m34p-749j-x6m6\n","assigner":"GitHub_M","epss":0.4,"enisaIdProduct":[{"id":"a88c4bc7-39e5-33c2-9bc5-2f4064fcebf7","product":{"name":"js-toml","vendor":{"name":"sunnyadn"}},"product_version":"\u003c 1.1.2"}],"enisaIdVendor":[{"id":"babf4b2c-a62f-35f7-97f2-12fb306fed82","vendor":{"name":"sunnyadn"}}],"enisaIdVulnerability":[{"id":"9db405eb-d0d8-345b-b17f-462f14f3828f","vulnerability":{"id":"CVE-2026-50029","description":"js-toml is a TOML parser for JavaScript, Prior to version 1.1.2, the interpreter checks whether a key already exists in a parser-built container with `if (object[key])` instead of `if (key in object)`. When the prior value is a falsy primitive — `false`, `0`, `0n`, `0.0`, `-0`, or `\"\"` — the duplicate-key branch is skipped and the value is silently overwritten by a later sub-table, dotted-key sub-table, or array-of-tables sharing the same name. Per the TOML 1.0.0 spec (\"Defining a key multiple times is invalid\"; \"You cannot define any key or table more than once\"), this should be a parse error. The result is structural type confusion of attacker-named keys in the value returned by `load()`. A boolean-typed `false` (or numeric `0`) becomes a truthy object. Host applications that gate behavior on `if (config.flag)`, `if (!user.banned)`, `if (config.allowDelete)`, or `if (config.publicMode)` will silently take the truthy branch. This is distinct from GHSA-65fc-cr5f-v7r2 (the 1.0.2 prototype-pollution fix). `Object.prototype` is not polluted. The `Object.create(null)` mitigation from 1.0.2 is intact; the bug here is in the duplicate-key state machine, not in container construction. Version 1.1.2 patches the incorrect comparison.","datePublished":"Aug 14, 2026, 7:08:54 PM","dateUpdated":"Aug 17, 2026, 7:34:15 PM","status":"PUBLISHED","baseScore":5.3,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","references":"https://github.com/sunnyadn/js-toml/security/advisories/GHSA-m34p-749j-x6m6\nhttps://github.com/sunnyadn/js-toml/commit/e0504fa5d3dcde2d1d588c9001c24b7b700beeeb\nhttps://github.com/sunnyadn/js-toml/releases/tag/v1.1.2\n","enisa_id":"EUVD-2026-58791\n","assigner":"GitHub_M","epss":0.4,"dataProcessed":"Nov 15, 2026, 7:19:28 AM","vulnerabilityProduct":[{"id":"2a0b501b-6832-3d84-85ae-603322d76635","product":{"name":"js-toml","vendor":{"name":"sunnyadn"}},"product_version":"\u003c 1.1.2"}],"vulnerabilityVendor":[{"id":"9cfc8d8a-09e0-3b2f-89f6-1101af46c153","vendor":{"name":"sunnyadn"}}]}},{"id":"e66d46a1-091d-357e-bea3-86579cb19514","vulnerability":{"id":"GHSA-m34p-749j-x6m6","description":"js-toml has silent type confusion via falsy-primitive duplicate-key bypass","datePublished":"Jun 26, 2026, 10:49:28 PM","dateUpdated":"Jul 21, 2026, 5:23:38 PM","baseScore":0.0,"references":"https://github.com/sunnyadn/js-toml/security/advisories/GHSA-m34p-749j-x6m6\nhttps://github.com/sunnyadn/js-toml/commit/e0504fa5d3dcde2d1d588c9001c24b7b700beeeb\nhttps://github.com/sunnyadn/js-toml\nhttps://github.com/sunnyadn/js-toml/releases/tag/v1.1.2\n","enisa_id":"EUVD-2026-58791\n","aliases":"CVE-2026-50029\nGHSA-m34p-749j-x6m6\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:51:29 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}}],"enisaIdAdvisory":[]}