{"answers":{"affected":"2 open source packages ship an affected version, including form-data-objectizer.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46510 exists.","fix":"Upgrade form-data-objectizer to 1.0.1 or later.","what":"CVE-2026-46510 is a high-severity code injection vulnerability in kaspernj form-data-objectizer, published on 29 May 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-46510 and fix it if it is affected.\n\nWhat it is: CVE-2026-46510 is a high-severity code injection vulnerability in kaspernj form-data-objectizer, published on 29 May 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-46510 exists.\n\nAffected packages and fixed versions:\n- form-data-objectizer (npm): affected all versions; fixed in 1.0.1\n- form-data-objectizer (npm): affected all versions; fixed in 1.0.1\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-46510/ (Markdown: https://insights.sbomify.com/CVE-2026-46510/index.md)","id":"CVE-2026-46510","markdown":"https://insights.sbomify.com/CVE-2026-46510/index.md","name":"CVE-2026-46510","record":{"aliases":["GHSA-m2hg-wjq3-28wq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js form data library","requires_auth":"none","summary":"Prototype pollution in form-data-objectizer allows attackers to mutate Object.prototype via crafted form keys, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"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":"form-data-objectizer converts FormData to object. Prior to 1.0.1, form-data-objectizer walks bracket-notation form keys (e.g. name[sub]) into nested objects without filtering __proto__, constructor, or prototype. A single HTTP form field whose name starts with __proto__[...] causes the library to mutate Object.prototype, which is a prototype pollution primitive of the entire Node.js process. This vulnerability is fixed in 1.0.1.","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":"Prototype pollution in form-data-objectizer via bracket-notation form keys","id":"CVE-2026-46510","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"HAXcms: Mass Token Exfiltration and Cross-Tenant Hijack","id":"CVE-2026-46511"},"packages":[{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"form-data-objectizer","purl":null,"source":"GHSA-m2hg-wjq3-28wq"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"form-data-objectizer","purl":"pkg:npm/form-data-objectizer","source":"GHSA-m2hg-wjq3-28wq"}],"prev":{"headline":"deepobj: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')","id":"CVE-2026-46509"},"products":["form-data-objectizer"],"published":"2026-05-29","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-06-02","vendors":["kaspernj"]},"summary":"Prototype pollution in form-data-objectizer allows attackers to mutate Object.prototype via crafted form keys, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-46510/"}