dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-9844

HIGH · 8.8 CVSS v3.1 Published 2025-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Uncontrolled Search Path Element vulnerability in Salesforce Salesforce CLI on Windows allows Replace Trusted Executable.This issue affects Salesforce CLI: before 2.106.6.

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

An Uncontrolled Search Path Element vulnerability in Salesforce CLI on Windows allows an attacker to replace a trusted executable. This occurs when the application uses an insufficiently qualified path to locate executable files, potentially allowing a malicious binary to be executed in place of the legitimate one.

MitigationUpdate Salesforce CLI to version 2.106.6 or later on all Windows installations. Prioritize systems where the CLI runs with elevated privileges.

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

CVSS:3.1/AV:N/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 Windows operating system
    Run 'systeminfo | findstr /B /C:"OS Name"' or check system properties. This vulnerability only affects Windows versions of Salesforce CLI.
    Affected if The system is running Windows and has Salesforce CLI installed below version 2.106.6.
  2. Locate Salesforce CLI installation
    Run 'where sfdx' or 'where sf' in Command Prompt, or check common installation paths such as C:\Program Files\sf or %LOCALAPPDATA%\sf. Also check for sfdx executable.
    Affected if Salesforce CLI executable is found on the system.
  3. Determine installed Salesforce CLI version
    Run 'sfdx version' or 'sf version' from Command Prompt or PowerShell. Record the version number displayed.
    Affected if The version returned is lower than 2.106.6 (for example, 2.106.5, 2.105.0, etc.).
  4. Verify version is within affected range
    Compare the installed version to the fixed version 2.106.6. Versions 2.106.5 and below are affected; versions 2.106.6 and later are not.
    Affected if Installed version is 2.106.5 or earlier, or any version below 2.106.6.

A user is affected if they are running Salesforce CLI on Windows with a version lower than 2.106.6, as the application will search attacker-controlled paths before legitimate locations.

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

Update Salesforce CLI to version 2.106.6 or later on all Windows installations. Prioritize systems where the CLI runs with elevated privileges.

Recommended fix High confidence

Salesforce CLI version 2.106.6 or later on Windows

  1. Check the current Salesforce CLI version by running: sf version
  2. Update Salesforce CLI to the latest version by running: sf update
  3. Alternatively, download and install the latest Salesforce CLI installer from the official Salesforce website
  4. Verify the installed version is 2.106.6 or later by running: sf version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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