# CVE-2025-9844: Path traversal in Salesforce CLI

> An attacker can replace a trusted executable via uncontrolled search path, leading to code execution on Windows systems using Salesforce CLI.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-p96x-fw5c-mhr8

## What is CVE-2025-9844?

CVE-2025-9844 is a high-severity path traversal vulnerability in Salesforce CLI, published on 23 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Uncontrolled Search Path Element vulnerability in Salesforce Salesforce CLI on Windows allows Replace Trusted Executable.This issue affects Salesforce CLI: before 2.106.6.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2025-9844 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9844 is a high-severity path traversal vulnerability in Salesforce CLI, published on 23 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9844 in the wild and no public exploit code.

Affected product: Salesforce CLI. 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-9844/ (Markdown: https://insights.sbomify.com/CVE-2025-9844/index.md)
```

## Sources

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

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