CVE-2026-50029: Js toml Js-toml Has Silent Type Confusion Vulnerability
MODERATECVE-2026-50029 is a MODERATE (CVSS 5.3) js-toml has silent type confusion vulnerability (CWE-697: Incorrect Comparison) affecting Js toml libraries in the npm ecosystem. The issue involves js-toml has silent type confusion via falsy-primitive duplicate-key bypass. Remediation is available by upgrading affected packages to version 1.1.2.
CVE-2026-50029 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).
How to Fix CVE-2026-50029
To remediate this vulnerability, upgrade all affected Js toml dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install js-toml@1.1.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls js-toml
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-50029, inspect your project dependencies using npm:
npm ls js-toml
Analyze the terminal output to locate any version of Js toml in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.2), your application is affected.
Note: The npm ls js-toml command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-697: Incorrect Comparison, where the product compares two entities in a security-relevant context, but the comparison is incorrect. In Js toml, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-50029 Affected Js toml Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
js-toml
|
npm |
< 1.1.2
|
1.1.2
|
References
Frequently Asked Questions
What is CVE-2026-50029?
Which Js toml versions are affected?
What version fixes CVE-2026-50029?
Is js-toml affected?
What is the CVSS score of CVE-2026-50029?
What CWE is associated with CVE-2026-50029?
How can I check npm dependencies for CVE-2026-50029?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m34p-749j-x6m6",
"modified" : "2026-07-21T17:23:38Z",
"published" : "2026-06-26T22:49:28Z",
"aliases" : [ "CVE-2026-50029" ],
"summary" : "js-toml has silent type confusion via falsy-primitive duplicate-key bypass",
"details" : "### Summary\n\n`js-toml`'s 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.\n\nThe 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.\n\nThis is **distinct** from [GHSA-65fc-cr5f-v7r2](https://github.com/sunnyadn/js-toml/security/advisories/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.\n\n### Details\n\nTwo truthy checks are wrong:\n\n`src/load/interpreter.ts:214` — `Interpreter.tryCreatingObject`\n\n```js\nif (object[key]) { // falsy primitives slip through\n // duplicate-key logic\n} else {\n object[key] = createSafeObject(); // silently overwrites the prior falsy value\n ...\n}\n```\n\n`src/load/interpreter.ts:278` — `Interpreter.getOrCreateArray`\n\n```js\nif (object[first] && !Array.isArray(object[first])) { // same flaw\n throw new DuplicateKeyError();\n}\nobject[first] = object[first] || []; // overwrites the prior falsy value\n```\n\nBoth should use the `in` operator. Containers are created via `Object.create(null)`, so `in` is unambiguous (no inherited keys to worry about).\n\nThe bug is reachable through every parent-walking interpreter path:\n\n- `assignValue` — dotted keys in `key = value`\n- `createTable` — `[stdTable]` headers\n- `getOrCreateArray` — `[[arrayOfTables]]` headers\n\n### PoC\n\n```toml\nisAdmin = false\n[isAdmin]\nforced = \"yes\"\n```\n\n```js\nimport { load } from 'js-toml';\n\nconst config = load(`\nisAdmin = false\n[isAdmin]\nforced = \"yes\"\n`);\n\nconsole.log(JSON.stringify(config));\n// {\"isAdmin\":{\"forced\":\"yes\"}}\n\nconsole.log(config.isAdmin ? 'BYPASS' : 'safe');\n// BYPASS\n\nif (config.isAdmin) {\n // attacker reaches admin-only code\n}\n```\n\n### Impact\n\nSpec-violating input acceptance leading to structural type confusion. (CWE-697)\n\n### Suggested fix\n\nin `src/load/interpreter.ts`\n\n```diff\nexport class Interpreter extends BaseCstVisitor {\n ignoreImplicitDeclared,\n ignoreExplicitDeclared\n ) {\n- if (object[key]) {\n+ if (key in object) {\n if (\n !isPlainObject(object[key]) ||\n (!ignoreExplicitDeclared &&\n```\n```diff\nexport class Interpreter extends BaseCstVisitor {\n return this.getOrCreateArray(keys, object[first], idx + 1);\n }\n\n- if (object[first] && !Array.isArray(object[first])) {\n+ if (first in object && !Array.isArray(object[first])) {\n throw new DuplicateKeyError();\n }\n\n object[first] = object[first] || [];\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "js-toml"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.1.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.1.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/sunnyadn/js-toml/security/advisories/GHSA-m34p-749j-x6m6"
}, {
"type" : "WEB",
"url" : "https://github.com/sunnyadn/js-toml/commit/e0504fa5d3dcde2d1d588c9001c24b7b700beeeb"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/sunnyadn/js-toml"
}, {
"type" : "WEB",
"url" : "https://github.com/sunnyadn/js-toml/releases/tag/v1.1.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-697" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-26T22:49:28Z",
"nvd_published_at" : null
}
}