dbcve.org
CWE-426Weakness · CWE-426

CVE-2025-9267

HIGH · 7.0 CVSS v4.0 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated

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
In Seagate Toolkit on Windows a vulnerability exists in the Toolkit Installer prior to versions 2.35.0.6 where it attempts to load DLLs from the current working directory without validating their origin or integrity. This behavior can be exploited by placing a malicious DLL in the same directory as the installer executable, leading to arbitrary code execution with the privileges of the user running the installer. The issue stems from the use of insecure DLL loading practices, such as relying on relative paths or failing to specify fully qualified paths when invoking system libraries.

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

The Seagate Toolkit Installer for Windows prior to version 2.35.0.6 is vulnerable to DLL hijacking. The installer attempts to load dynamic link libraries from the current working directory without validating their origin or integrity, using insecure relative paths instead of fully qualified paths. An attacker can place a malicious DLL in the same directory as the installer executable to achieve arbitrary code execution with the privileges of the user running the installer.

MitigationUpgrade the Seagate Toolkit Installer to version 2.35.0.6 or later, which implements secure DLL loading practices with fully qualified paths. Avoid running the installer from untrusted or shared directories.

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
High
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 the Seagate Toolkit Installer executable
    Search for files named 'SeagateToolkitSetup.exe', 'Seagate Toolkit Installer.exe', or similar patterns in Program Files, Program Files (x86), Downloads folder, and recent download directories using File Explorer search or Get-ChildItem -Recurse
    Affected if The installer executable exists on the system at any location
  2. Check the installed version of the Seagate Toolkit Installer
    Right-click the installer executable, select Properties, then go to the Details tab to view the File Version. Alternatively, run 'Get-Item -Path "<path_to_installer>" | Select-Object Name, VersionInfo' in PowerShell
    Affected if File version is lower than 2.35.0.6 or cannot be determined (indicating an old installer)
  3. Verify the installer has not been patched to a secure version
    Compare the discovered version number to 2.35.0.6 - versions 2.35.0.6 and later contain the fix for insecure DLL loading
    Affected if Version is present and is less than 2.35.0.6, making it vulnerable to DLL hijacking when run from an attacker-controlled directory

You are affected if the Seagate Toolkit Installer version on your system is found to be earlier than 2.35.0.6, as those versions contain the DLL hijacking 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Seagate Toolkit Installer to version 2.35.0.6 or later, which implements secure DLL loading practices with fully qualified paths. Avoid running the installer from untrusted or shared directories.

Recommended fix High confidence

2.35.0.6

  1. Download the Seagate Toolkit Installer version 2.35.0.6 or later from the official Seagate website
  2. Verify the digital signature of the installer before running it
  3. Uninstall any existing version of Seagate Toolkit
  4. Run the updated installer with version 2.35.0.6 or newer
  5. Confirm the installed version displays 2.35.0.6 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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