# CVE-2025-9267: Other in Toolkit

> Attackers can execute arbitrary code by placing a malicious DLL in the installer's directory, affecting Seagate Toolkit users on Windows.

- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-6rrf-p74p-p7q8

## What is CVE-2025-9267?

CVE-2025-9267 is a high-severity vulnerability in Seagate Toolkit, published on 26 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-427 (Uncontrolled Search Path Element), CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2025-9267?


## How do I fix CVE-2025-9267?

No fix has been published for CVE-2025-9267 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9267 being exploited?

There is no known exploitation of CVE-2025-9267 in the wild and no public exploit code.

Public exploit code:

- Seagate Toolkit for Windows (Installer <2.35.0.6) is vulnerable to insecure DLL loading. The installer loads DLLs from the working directory without validation, allowing attackers to place a malicious DLL alongside the installer and execute arbitrary code. (github_poc): https://github.com/Tiger3080/CVE-2025-9267

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9267 and fix it if it is affected.

What it is: CVE-2025-9267 is a high-severity vulnerability in Seagate Toolkit, published on 26 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-9267 in the wild and no public exploit code.

Affected product: Seagate Toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9267/ (Markdown: https://insights.sbomify.com/CVE-2025-9267/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9267
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9267
- OSV: https://osv.dev/vulnerability/CVE-2025-9267

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9267/
Summaries are generated and may contain mistakes; the official description above is the record.