{"answers":{"affected":"2 open source packages ship an affected version, including toml.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63376 exists.","fix":"Upgrade toml to 4.1.2 or later.","what":"CVE-2026-63376 is a high-severity unsafe deserialization vulnerability in BinaryMuse toml-node, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63376 and fix it if it is affected.\n\nWhat it is: CVE-2026-63376 is a high-severity unsafe deserialization vulnerability in BinaryMuse toml-node, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63376 exists.\n\nAffected packages and fixed versions:\n- toml (npm): affected all versions; fixed in 4.1.2\n- toml (npm): affected all versions; fixed in 4.1.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63376/ (Markdown: https://insights.sbomify.com/CVE-2026-63376/index.md)","id":"CVE-2026-63376","markdown":"https://insights.sbomify.com/CVE-2026-63376/index.md","name":"CVE-2026-63376","record":{"aliases":["CLEANSTART-2026-GB44071","ECHO-5068-33f0-0422","GHSA-v5mp-jgw5-2x6j","MINI-v5xf-x5r4-hmp5","ROOT-APP-NPM-CVE-2026-63376"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js TOML parser","requires_auth":"none","summary":"Attackers can pollute Object.prototype via crafted TOML input, potentially leading to code execution or denial of service in applications using the library.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"toml-node is a TOML parser for Node.js and the browser. Prior to 4.1.2, toml.parse() in lib/compiler.js can be tricked by a table path such as a.b.y.__proto__.__proto__, allowing traversal from a scalar value into Number.prototype and Object.prototype. The currentPath tracking value uses both arrays and strings, so valueAssignments records a comma-joined path such as a,b.y while deepRef checks the dot-joined path a.b.y, allowing the duplicate-key guard to miss and attacker-controlled keys to be written to Object.prototype. A table-array prefix-clearing path in addTableArray can also erase guard state before the same __proto__ traversal. Injected properties become visible throughout the Node.js process and can cause denial of service, logic or authorization bypass, or code execution when an application contains a suitable gadget. This issue is fixed in version 4.1.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"toml-node: Prototype Pollution Leads to `Object.prototype` Corruption via `__proto__` Key-Path Desynchronization","id":"CVE-2026-63376","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Libevent: HTTP Header smuggling","id":"CVE-2026-63379"},"packages":[{"ecosystem":"npm","fixed":["4.1.2"],"introduced":["0"],"last_affected":[],"package":"toml","purl":null,"source":"GHSA-v5mp-jgw5-2x6j"},{"ecosystem":"npm","fixed":["4.1.2"],"introduced":["0"],"last_affected":[],"package":"toml","purl":"pkg:npm/toml","source":"GHSA-v5mp-jgw5-2x6j"}],"prev":{"headline":"AnyIO: TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing","id":"CVE-2026-63374"},"products":["toml-node"],"published":"2026-09-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-05","vendors":["BinaryMuse"]},"summary":"Attackers can pollute Object.prototype via crafted TOML input, potentially leading to code execution or denial of service in applications using the library.","url":"https://insights.sbomify.com/CVE-2026-63376/"}