Skip to main content
VulnerabilityPublished

CVE-2025-61861: FUJI ELECTRIC CO., LTD. / Hakko Electronics V-SFT · Out-of-bounds Read

Affects FUJI ELECTRIC CO., LTD. / Hakko Electronics V-SFTSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
FUJI ELECTRIC CO., LTD. / Hakko Electronics Co., Ltd. V-SFTAffected
  • <=6.2.7.0
Fixed in–

AI-suggested

  1. Monitor FUJI ELECTRIC and Hakko Electronics official channels for patches addressing CVE-2025-61861 and apply them promptly once released.
  2. Until patches are available, restrict access to V-SFT software and its associated file types to trusted users only.
  3. Implement strict file handling policies to prevent opening untrusted or unsolicited V-SFT files, including user training to recognize suspicious files.
  4. Use application whitelisting and endpoint protection solutions to detect and block abnormal behavior related to V-SFT processes.
  5. Employ network segmentation to isolate systems running V-SFT from general user environments to reduce the risk of malicious file delivery.
  6. Conduct regular audits of file access and monitor logs for unusual activity involving V-SFT files.
  7. Consider deploying sandbox environments to analyze suspicious V-SFT files before allowing them on production systems.
  8. Enhance user awareness programs focusing on social engineering risks that could lead to opening malicious files.

Description

An out-of-bounds read vulnerability exists in VS6ComFile!load_link_inf 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.

References

Community reviews

Loading reviews…