dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-50130

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
A heap-based buffer overflow vulnerability exists in VS6Sim.exe contained in V-SFT and TELLUS provided by FUJI ELECTRIC CO., LTD. Opening V9 files or X1 files specially crafted by an attacker on the affected product may lead to arbitrary code execution.

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 · high confidence

A heap-based buffer overflow vulnerability exists in VS6Sim.exe, a component of V-SFT and TELLUS software provided by FUJI ELECTRIC CO., LTD. The vulnerability is triggered when the application opens specially crafted V9 or X1 files, which can cause memory corruption on the heap. Successful exploitation allows an attacker to execute arbitrary code on the affected system.

MitigationOrganizations should avoid opening untrusted or unverified V9 and X1 files in affected products. Implement network segmentation and apply vendor patches when available. Consider disabling VS6Sim.exe or restricting its use to trusted files until a patch is released.

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

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
High
Availability
High

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

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. Locate VS6Sim.exe component
    Search for VS6Sim.exe in V-SFT and TELLUS installation directories, or use system file search commands (e.g., Get-ChildItem -Recurse -Filter VS6Sim.exe on Windows)
    Affected if VS6Sim.exe is found on the system
  2. Identify installed V-SFT or TELLUS version
    Check installed programs list or product About/Version information within V-SFT or TELLUS software from FUJI ELECTRIC CO., LTD
    Affected if Any version of V-SFT or TELLUS with VS6Sim.exe is installed
  3. Confirm V9 or X1 file handling is enabled
    Review application file type associations or default settings to verify the software processes V9 or X1 file formats
    Affected if The software is configured to open V9 or X1 files
  4. Check for VS6Sim.exe execution context
    Verify VS6Sim.exe is accessible and not explicitly disabled through application settings or group policy
    Affected if VS6Sim.exe can be invoked by the application

If V-SFT or TELLUS software with VS6Sim.exe is installed and processes V9 or X1 files, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should avoid opening untrusted or unverified V9 and X1 files in affected products. Implement network segmentation and apply vendor patches when available. Consider disabling VS6Sim.exe or restricting its use to trusted files until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50130 — 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-2025-50130 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