{"answers":{"affected":"2 open source packages ship an affected version, including parse-nested-form-data.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45302 exists.","fix":"Upgrade parse-nested-form-data to 1.0.1 or later.","what":"CVE-2026-45302 is a high-severity vulnerability in milamer parse-nested-form-data, published on 1 Jun 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-45302 and fix it if it is affected.\n\nWhat it is: CVE-2026-45302 is a high-severity vulnerability in milamer parse-nested-form-data, published on 1 Jun 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-45302 exists.\n\nAffected packages and fixed versions:\n- parse-nested-form-data (npm): affected all versions; fixed in 1.0.1\n- parse-nested-form-data (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-45302/ (Markdown: https://insights.sbomify.com/CVE-2026-45302/index.md)","id":"CVE-2026-45302","markdown":"https://insights.sbomify.com/CVE-2026-45302/index.md","name":"CVE-2026-45302","record":{"aliases":["GHSA-xp7r-j8r6-j9h3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js FormData parser","requires_auth":"none","summary":"Prototype pollution in parse-nested-form-data allows attackers to modify Object.prototype via crafted FormData field names, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"other"},"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":"parse-nested-form-data is a tiny node module for parsing FormData by name into objects and arrays. Prior to version 1.0.1, parseFormData() walks bracket and dot-notation FormData field names into nested objects without filtering reserved property keys. A single FormData field whose name begins with __proto__, or contains .__proto__. mid-path, causes the parser to traverse onto Object.prototype and assign properties there, polluting the prototype chain of every plain object in the running process. This issue has been patched in version 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 parse-nested-form-data via `__proto__` in FormData field names","id":"CVE-2026-45302","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Open WebUI: Stored XSS via the HTML renedering view","id":"CVE-2026-45303"},"packages":[{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"parse-nested-form-data","purl":null,"source":"GHSA-xp7r-j8r6-j9h3"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"parse-nested-form-data","purl":"pkg:npm/parse-nested-form-data","source":"GHSA-xp7r-j8r6-j9h3"}],"prev":{"headline":"Open WebUI: Missing permission check in files API allows authenticated users to list, access and delete every uploaded file","id":"CVE-2026-45301"},"products":["parse-nested-form-data"],"published":"2026-06-01","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":["milamer"]},"summary":"Prototype pollution in parse-nested-form-data allows attackers to modify Object.prototype via crafted FormData field names, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-45302/"}