{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94091 exists.","fix":"No fix has been published for CVE-2026-94091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-94091 is a medium-severity unsafe deserialization vulnerability in piskvorky gensim, published on 20 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-94091 and fix it if it is affected.\n\nWhat it is: CVE-2026-94091 is a medium-severity unsafe deserialization vulnerability in piskvorky gensim, published on 20 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94091 exists.\n\nAffected product: piskvorky gensim. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-94091/ (Markdown: https://insights.sbomify.com/CVE-2026-94091/index.md)","id":"CVE-2026-94091","markdown":"https://insights.sbomify.com/CVE-2026-94091/index.md","name":"CVE-2026-94091","record":{"aliases":["GHSA-9h85-xr59-9fh8"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python NLP library","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary code via unsafe pickle deserialization in the gensim model loader, requiring immediate mitigation as no official fix is available.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A weakness has been identified in piskvorky gensim up to 4.4.0. The impacted element is the function Load of the file gensim/utils.py of the component Model Loader. This manipulation of the argument fname causes deserialization. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Maintainer closed #3663 same-day with no comment, PR, or fix; repo's last push (2025-11-01) predates the report, so the unsafe pickle.load in SaveLoad.load remains unguarded at develop HEAD.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"piskvorky gensim Model Loader utils.py load deserialization","id":"CVE-2026-94091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"dmlc dgl utils.py _read_torch_data deserialization","id":"CVE-2026-94092"},"packages":[],"prev":{"headline":"JusticeRage Manalyze PE Parser pe.cpp _parse_debug integer underflow","id":"CVE-2026-94090"},"products":["gensim"],"published":"2026-09-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["piskvorky"]},"summary":"Remote attackers can execute arbitrary code via unsafe pickle deserialization in the gensim model loader, requiring immediate mitigation as no official fix is available.","url":"https://insights.sbomify.com/CVE-2026-94091/"}