{"answers":{"affected":"2 open source packages ship an affected version, including ts-fns.","exploited":"There is no known exploitation of CVE-2025-57351 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-57351 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-57351 is a medium-severity code injection vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-57351 and fix it if it is affected.\n\nWhat it is: CVE-2025-57351 is a medium-severity code injection vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-57351 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ts-fns (npm): affected all versions up to 13.1.3; no fix listed\n- ts-fns (npm): affected all versions up to 13.1.3; no fix listed\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-2025-57351/ (Markdown: https://insights.sbomify.com/CVE-2025-57351/index.md)","id":"CVE-2025-57351","markdown":"https://insights.sbomify.com/CVE-2025-57351/index.md","name":"CVE-2025-57351","record":{"aliases":["GHSA-g7wq-wggw-vmhg"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Attackers can inject properties into the global prototype via the assign function, potentially causing crashes, unexpected code execution, or security bypasses.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"A prototype pollution vulnerability exists in the ts-fns package versions prior to 13.0.7, where insufficient validation of user-provided keys in the assign function allows attackers to manipulate the Object.prototype chain. By leveraging this flaw, adversaries may inject arbitrary properties into the global object's prototype, potentially leading to application crashes, unexpected code execution behaviors, or bypasses of security-critical validation logic dependent on prototype integrity. The vulnerability stems from improper handling of deep property assignment operations within the library's public API functions. This issue remains unaddressed in the latest available version.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ts-fns has prototype pollution vulnerability","id":"CVE-2025-57351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"min-document vulnerable to prototype pollution","id":"CVE-2025-57352"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["13.1.3"],"package":"ts-fns","purl":null,"source":"GHSA-g7wq-wggw-vmhg"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["13.1.3"],"package":"ts-fns","purl":"pkg:npm/ts-fns","source":"GHSA-g7wq-wggw-vmhg"}],"prev":{"headline":"CSVTOJSON has a prototype pollution vulnerability","id":"CVE-2025-57350"},"products":["n/a"],"published":"2025-09-24","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-25","vendors":["n/a"]},"summary":"Attackers can inject properties into the global prototype via the assign function, potentially causing crashes, unexpected code execution, or security bypasses.","url":"https://insights.sbomify.com/CVE-2025-57351/"}