GHSA-6W87-G839-9WV7

Workarounds

No workaround available

References

N/A

For more information

If you have any questions or comments about this advisory:

• Open an issue in the Argo CD issue tracker or discussions
• Join us on Slack in channel #argo-cd

Credits

This vulnerability was found and reported by a third-party who wishes to stay anonymous. We want to thank this third-party for disclosing this vulnerability to us in a responsible manner.

When Argo CD was connected to a Helm OCI repository with authentication enabled, the credentials used for accessing the remote repository were logged.

Anyone with access to the pod logs - either via access with appropriate permissions to the Kubernetes control plane or a third party log management system where the logs from Argo CD were aggregated - could have potentially obtained the credentials to the Helm OCI repository.

If you are using Helm OCI repositories with Argo CD, it is strongly recommended to upgrade Argo CD to the latest patch version and to change the credentials used to access the repositories.

GHSA-6W87-G839-9WV7 has a CVSS score of 6.6 (Medium). The vector is requires local access, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.14, 1.8.7); upgrading removes the vulnerable code path.

Kodem intelligence

A patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.

1. What is GHSA-6W87-G839-9WV7? GHSA-6W87-G839-9WV7 is a medium-severity security vulnerability in github.com/argoproj/argo-cd (go), affecting versions < 1.7.14. It is fixed in 1.7.14, 1.8.7.
2. How severe is GHSA-6W87-G839-9WV7? GHSA-6W87-G839-9WV7 has a CVSS score of 6.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/argoproj/argo-cd are affected by GHSA-6W87-G839-9WV7? github.com/argoproj/argo-cd (go) versions < 1.7.14 is affected.
4. Is there a fix for GHSA-6W87-G839-9WV7? Yes. GHSA-6W87-G839-9WV7 is fixed in 1.7.14, 1.8.7. Upgrade to this version or later.
5. Is GHSA-6W87-G839-9WV7 exploitable, and should I be worried? Whether GHSA-6W87-G839-9WV7 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
6. What actually determines whether GHSA-6W87-G839-9WV7 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.
7. How do I fix GHSA-6W87-G839-9WV7?
   • Upgrade github.com/argoproj/argo-cd to 1.7.14 or later
   • Upgrade github.com/argoproj/argo-cd to 1.8.7 or later

Other vulnerabilities in github.com/argoproj/argo-cd