dbcve.org
Factorytalk LinxApplication · Rockwellautomation

CVE-2025-9067

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 6.50 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 security issue exists within the x86 Microsoft Installer File (MSI), installed with FTLinx. Authenticated attackers with valid Windows user credentials can initiate a repair and hijack the resulting console window. This allows the launching of a command prompt running with SYSTEM-level privileges, allowing full access to all files, processes, and system resources.

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

The FTLinx MSI installer contains a vulnerability where the repair function spawns a console window running with SYSTEM-level privileges. An authenticated Windows user with valid credentials can trigger a repair operation and hijack this console window to obtain a command prompt with full SYSTEM access, enabling complete control over files, processes, and system resources.

MitigationApply vendor-supplied patch when available; until then, restrict Windows user repair permissions on systems with FTLinx installed and monitor for unauthorized repair operations.

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
Factorytalk LinxApplication
Affected:< 6.50

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Confirm Factorytalk Linx installation
    Check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'FactoryTalk Linx' or use PowerShell: Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*FactoryTalk Linx*'}
    Affected if No entry found means the product is not installed and the system is not affected
  2. Determine installed version
    Query the registry value 'DisplayVersion' from the FactoryTalk Linx uninstall entry found in the previous step, or use: (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*FactoryTalk Linx*'}).DisplayVersion
    Affected if Version cannot be determined - further manual investigation required
  3. Compare version to affected range
    Compare the discovered version number to 6.50. Versions below 6.50 (such as 6.40, 6.30, etc.) are affected. Versions 6.50 and above are not affected.
    Affected if Installed version is less than 6.50 (for example: 6.40.0, 6.30.1, etc.)
  4. Verify repair operation accessibility
    On affected versions, any authenticated Windows user can trigger an MSI repair by running: msiexec /f {product-code} or by right-clicking the installed program in Add/Remove Programs and selecting 'Repair'. The vulnerability allows hijacking the SYSTEM-privileged console window that spawns during repair.
    Affected if User has Windows credentials and can access the repair function on a system with FactoryTalk Linx version < 6.50

The environment is affected if FactoryTalk Linx is installed with a version number lower than 6.50 and any authenticated user can trigger the MSI repair operation.

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 6.50 or later
Fixed in 6.50
Interim mitigation

Apply vendor-supplied patch when available; until then, restrict Windows user repair permissions on systems with FTLinx installed and monitor for unauthorized repair operations.

Recommended fix High confidence

Factorytalk Linx 6.50

  1. Download Factorytalk Linx version 6.50 or later from the official Rockwell Automation website (https://www.rockwellautomation.com)
  2. Verify the downloaded installer matches the expected hash if provided in release notes
  3. Close all applications that may be using Factorytalk Linx services
  4. Run the Factorytalk Linx 6.50 installer as an administrator
  5. Follow the on-screen installation wizard prompts to complete the upgrade
  6. Restart any Factorytalk services if prompted after installation
  7. Verify the installation was successful by checking the version number in the Factorytalk Linx properties or About dialog
Caveat Review Rockwell Automation release notes for any feature changes or migration considerations between your current version and 6.50

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

Fix this in Factorytalk Linx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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