{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32925 is a high-severity memory corruption vulnerability in FUJI ELECTRIC CO., LTD. / Hakko Electronics Co., Ltd. V-SFT, published on 1 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32925 and fix it if it is affected.\n\nWhat it is: CVE-2026-32925 is a high-severity memory corruption vulnerability in FUJI ELECTRIC CO., LTD. / Hakko Electronics Co., Ltd. V-SFT, published on 1 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32925 in the wild and no public exploit code.\n\nAffected product: FUJI ELECTRIC CO., LTD. / Hakko Electronics Co., Ltd. V-SFT. 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-32925/ (Markdown: https://insights.sbomify.com/CVE-2026-32925/index.md)","id":"CVE-2026-32925","markdown":"https://insights.sbomify.com/CVE-2026-32925/index.md","name":"CVE-2026-32925","record":{"aliases":["GHSA-257x-mvvc-g6ff"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"V-SFT software","requires_auth":"none","summary":"A stack-based buffer overflow in V-SFT allows arbitrary code execution when opening a crafted V7 file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"v-sft","vendor":"fujielectric"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"V-SFT versions 6.2.10.0 and prior contain a stack-based buffer overflow in VS6ComFile!CV7BaseMap::WriteV7DataToRom. Opening a crafted V7 file may lead to arbitrary code execution on the affected product.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in V-SFT","id":"CVE-2026-32925","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in V-SFT","id":"CVE-2026-32926"},"packages":[],"prev":{"headline":"OpenClaw \u003c 2026.3.12 - Authorization Bypass via Misclassified Reaction Events in Feishu","id":"CVE-2026-32924"},"products":["V-SFT"],"published":"2026-04-01","related":[{"cvss_score":8.4,"headline":"Information disclosure in V-SFT","id":"CVE-2026-32926","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":8.4,"headline":"Information disclosure in V-SFT","id":"CVE-2026-32927","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":8.4,"headline":"Memory corruption in V-SFT","id":"CVE-2026-32928","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":8.4,"headline":"Information disclosure in V-SFT","id":"CVE-2026-32929","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":7.8,"headline":"Memory corruption in V-SFT","id":"CVE-2022-26302","kev_date_added":null,"published":"2022-06-14"},{"cvss_score":7.8,"headline":"Memory corruption in V-SFT","id":"CVE-2022-29925","kev_date_added":null,"published":"2022-06-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["FUJI ELECTRIC CO., LTD. / Hakko Electronics Co., Ltd."]},"summary":"A stack-based buffer overflow in V-SFT allows arbitrary code execution when opening a crafted V7 file.","url":"https://insights.sbomify.com/CVE-2026-32925/"}