CVE-2025-61862: FUJI ELECTRIC CO., LTD. / Hakko Electronics V-SFT · Out-of-bounds Read
Affects FUJI ELECTRIC CO., LTD. / Hakko Electronics V-SFTSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FUJI ELECTRIC CO., LTD. / Hakko Electronics Co., Ltd. V-SFT | Affected
| Fixed in– |
AI-suggested
1. Monitor vendor communications closely and apply official patches or updates for V-SFT as soon as they become available. 2. Until patches are released, restrict the opening of V-SFT files to trusted sources only; implement strict file validation and scanning policies. 3. Limit user permissions on systems running V-SFT to reduce the risk of local exploitation and prevent unauthorized file execution. 4. Employ application whitelisting and endpoint detection and response (EDR) solutions to detect anomalous behaviors related to V-SFT processes. 5. Conduct user awareness training to prevent inadvertent opening of malicious files, emphasizing the risks of interacting with untrusted V-SFT files. 6. Isolate critical industrial control systems from general IT networks to minimize the risk of lateral movement by attackers. 7. Implement robust logging and monitoring to detect abnormal application crashes or suspicious activity indicative of exploitation attempts. 8. Review and harden system configurations to minimize attack surface, including disabling unnecessary services and enforcing strict access controls on affected systems.
Description
An out-of-bounds read vulnerability exists in VS6ComFile!get_ovlp_element_size of V-SFT v6.2.7.0 and earlier. Opening specially crafted V-SFT files may lead to information disclosure, affected system's abnormal end (ABEND), and arbitrary code execution.