Local directory executable lookup in sops (Windows-only)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Windows users using the sops direct editor option (sops file.yaml) can have a local executable named either vi, vim, or nano executed if running sops from cmd.exe This attack is only viable if an attacker is able to place a malicious binary within the directory you are running sops from. As well, this attack will only work when using cmd.exe or the Windows C library SearchPath function. This is a result of these Windows tools including . within their PATH by default. If you are using sops within untrusted directories on Windows via cmd.exe, please upgrade immediately As well, if you have . within your default $PATH, please upgrade immediately. More information can be found on the official Go blog: https://blog.golang.org/path-security Patches The problem has been resolved in v3.7.1 Now, if Windows users using cmd.exe run into this issue, a warning message will be printed: vim resolves to executable in current directory (.\vim.exe) References…

Published by the source

20 May 2021, 16:50 UTC

Last modified by the source

9 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x5c7-x7m2-rhmf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-x5c7-x7m2-rhmf

Advisory: Local directory executable lookup in sops (Windows-only)
IDs: GHSA-x5c7-x7m2-rhmf
Record: https://patchnext.com/advisories/ghsa-x5c7-x7m2-rhmf (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.mozilla.org/sops/v3 3.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.mozilla.org/sops/v3: affected < 3.7.1; fixed in 3.7.1

## Suggested inspection (read-only)
- Go go.mozilla.org/sops/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.mozilla.org/sops/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x5c7-x7m2-rhmf (GitHub-reviewed advisory GHSA-x5c7-x7m2-rhmf lists affected ranges: Go go.mozilla.org/sops/v3 >=0 <3.7.1)

Commands are suggestions: review each one before running it.