Fuji Electric V-SFT up to 6.2.10.0 WriteV7DataToRom stack-based overflow

Summaryinfo

A vulnerability was found in Fuji Electric V-SFT up to 6.2.10.0. It has been declared as critical. This affects the function CV7BaseMap::WriteV7DataToRom. The manipulation results in stack-based overflow. This vulnerability is known as CVE-2026-32925. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in Fuji Electric V-SFT up to 6.2.10.0. Affected is the function CV7BaseMap::WriteV7DataToRom. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at felib.fujielectric.co.jp. This vulnerability is traded as CVE-2026-32925 since 03/17/2026. The exploitability is told to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/02/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Fuji Electric

Name

• V-SFT

Version

• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10.0

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion