Summary
Local directory executable lookup in sops (Windows-only)
References
For more information
If you have any questions or comments about this advisory:
- Open a discussion in sops
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
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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)
Frequently Asked Questions
- What is GHSA-X5C7-X7M2-RHMF? GHSA-X5C7-X7M2-RHMF is a low-severity security vulnerability in go.mozilla.org/sops/v3 (go), affecting versions < 3.7.1. It is fixed in 3.7.1.
- Which versions of go.mozilla.org/sops/v3 are affected by GHSA-X5C7-X7M2-RHMF? go.mozilla.org/sops/v3 (go) versions < 3.7.1 is affected.
- Is there a fix for GHSA-X5C7-X7M2-RHMF? Yes. GHSA-X5C7-X7M2-RHMF is fixed in 3.7.1. Upgrade to this version or later.
- Is GHSA-X5C7-X7M2-RHMF exploitable, and should I be worried? Whether GHSA-X5C7-X7M2-RHMF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-X5C7-X7M2-RHMF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-X5C7-X7M2-RHMF? Upgrade
go.mozilla.org/sops/v3to 3.7.1 or later.