dbcve.org
V SftApplication · Fujielectric

CVE-2026-32926

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to after 6.2.10.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6ComFile!load_link_inf. Opening a crafted V7 file may lead to information disclosure from the affected product.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in the VS6ComFile!load_link_inf function when parsing V7 files. Opening a crafted malicious V7 file allows reading memory beyond allocated buffer boundaries, leading to information disclosure.

MitigationUsers should avoid opening V7 files from untrusted sources. If a patched version is available from the vendor, upgrade immediately. Implement file validation and consider network segmentation for systems running this software.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
V SftApplication
Affected:<= 6.2.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed V-SFT version
    Check the program version through the application's 'About' dialog, installer properties, or registry entries under the Fujielectric V Sft installation directory. Compare the version number to the affected range (<= 6.2.10.0)
    Affected if The installed version is 6.2.10.0 or any prior version
  2. Locate V7 file handling component
    Verify the presence of the VS6ComFile module or related components that handle V7 file parsing within the V-SFT installation directory
    Affected if The VS6ComFile module exists and handles V7 file operations
  3. Detect V7 file parsing capability
    Check if V-SFT is configured to automatically parse or import V7 files, or if users have the ability to open V7 files through the application
    Affected if V7 file parsing is enabled or accessible to users
  4. Inventory V7 files on system
    Search the system for V7 files, particularly in user-accessible directories, shared folders, or recent documents locations associated with V-SFT
    Affected if Unsolicited or unexpected V7 files are present that could have been opened by the application

You are affected if V-SFT version 6.2.10.0 or lower is installed and the application can parse V7 files, as the vulnerability triggers during V7 file processing in the load_link_inf function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.2.10.0
Interim mitigation

Users should avoid opening V7 files from untrusted sources. If a patched version is available from the vendor, upgrade immediately. Implement file validation and consider network segmentation for systems running this software.

Recommended fix Moderate confidence

Any version newer than 6.2.10.0 (contact vendor for specific latest stable release)

  1. 1. Identify the current installed version of V-SFT by checking the product documentation or About section
  2. 2. Confirm the current version is <= 6.2.10.0 (vulnerable)
  3. 3. Contact Fujielectric support or visit the official download page at felib.fujielectric.co.jp to obtain the latest version
  4. 4. Download the latest V-SFT version (ensure it is newer than 6.2.10.0)
  5. 5. Before installing the update, backup any existing V7 project files
  6. 6. Install the updated version following the vendor's installation instructions
  7. 7. Verify the update was successful by checking the new version number
  8. 8. Test that existing V7 files open correctly in the updated version
Caveat Review release notes for any compatibility changes with existing V7 project files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in V Sft Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32926 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32926 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data