Advisory record · GHSA-mv6w-j4xc-qpfw

Argo CD leaks repository credentials in user-facing error messages and in logs

CVSS 6.3 MediumEPSS 0.0087 · 59th percentile

Published by the GitHub Advisory Database at 8 Feb 2023, 22:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/argoproj/argo-cd/v2Go>=2.6.0-rc1, <2.6.12.6.1
Identifiers
GHSA-mv6w-j4xc-qpfw · BIT-argo-cd-2023-25163 · CVE-2023-25163 · GO-2023-1548
Weakness (CWE)
CWE-532
Published
8 Feb 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Argo CD versions from 2.6.0-rc1 before 2.6.1 leak repository access credentials in user-facing error messages and logs. A user with applications create or applications update RBAC access can trigger these errors when creating or updating an Application through the API, UI or CLI, and can then read the leaked credentials. Upgrade to Argo CD 2.6.1, which contains the fix; the advisory says upgrading is the only complete resolution.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0087, the 59th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 8 Feb 2023, 19:50 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:15 UTC First seen by agentprime
  3. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.