{"id":"GO-2023-1548","revision":null,"records":[{"revision":"a3cc7fba9372489c9fa1e76aec822676","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2023-25163","aliases":[],"title":"Argo CD leaks repository credentials in user-facing error messages and in logs","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.","state":0,"publishedAt":"2023-02-08T20:44:17.94+00:00","modifiedAt":"2025-03-10T21:14:27.698+00:00","affected":[{"ecosystem":"Vendor product","name":"argo-cd","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"argoproj\",\n                    \"product\": \"argo-cd\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 2.6.0-rc1, < 2.6.1\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","score":6.3,"severity":"MEDIUM"}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw","https://github.com/argoproj/argo-cd/issues/12309","https://github.com/argoproj/argo-cd/pull/12320","https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2023-25163","license":"CVE Program Terms of Use","key":"cve-program:CVE-2023-25163","identifiers":["CVE-2023-25163"]},"retained":false,"historicalAffected":[]},{"revision":"d206f02f570a4e7d88f2d67c27b5b272","observedAt":"2026-11-16T03:34:31.802+00:00","statement":{"source":"euvd","id":"EUVD-2023-0745","aliases":["CVE-2023-25163","GHSA-mv6w-j4xc-qpfw"],"title":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are…","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","score":6.3,"severity":null}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw","https://github.com/argoproj/argo-cd/issues/12309","https://github.com/argoproj/argo-cd/pull/12320","https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-0745","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Feb 8, 2023, 8:44:17 PM","dateUpdated":"Mar 10, 2025, 9:14:27 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2023-0745","identifiers":["EUVD-2023-0745","CVE-2023-25163","GHSA-mv6w-j4xc-qpfw"]},"retained":false,"historicalAffected":[]},{"revision":"b82c2f72be284319a7b9147ddb2abbac","observedAt":"2026-10-24T21:17:28.488+00:00","statement":{"source":"nvd","id":"CVE-2023-25163","aliases":[],"title":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are…","description":"Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.","state":0,"publishedAt":"2023-02-08T21:15:10.847+00:00","modifiedAt":"2026-06-17T05:40:48.95+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","score":6.3,"severity":"MEDIUM"},{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/","https://github.com/argoproj/argo-cd/issues/12309","https://github.com/argoproj/argo-cd/pull/12320","https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2023-25163","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Modified","weaknesses":["CWE-532"],"productCriteria":["cpe:2.3:a:argoproj:argo_cd:2.6.0:-:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc1:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc2:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc3:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc4:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc5:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc6:*:*:*:*:*:*","cpe:2.3:a:argoproj:argo_cd:2.6.0:rc7:*:*:*:*:*:*"],"sourceDates":{"published":"2023-02-08T21:15:10.847","lastModified":"2026-06-17T05:40:48.950"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2023-25163","identifiers":["CVE-2023-25163"]},"retained":false,"historicalAffected":[]},{"revision":"5f97ed99d2e742dea501b6f5599a4da1","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-mv6w-j4xc-qpfw","aliases":["BIT-argo-cd-2023-25163","CVE-2023-25163","GO-2023-1548"],"title":"Argo CD leaks repository credentials in user-facing error messages and in logs","description":"### Impact\nAll versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error.\n\nThe user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. \n\nIf the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway.\n\n### Patches\n\nA patch for this vulnerability has been released in the following Argo CD version:\n\n* v2.6.1\n\n### Workarounds\n\nThe only way to completely resolve the issue is to upgrade.\n\n#### Mitigations\n\nTo mitigate the issue, make sure that your repo credentials have only least necessary privileges. For example, the credentials should not have push access, and they should not have access to more resources than what Argo CD actually needs (for example, a whole GitHub org when only one repo is needed).\n\nTo further mitigate the impact of a leaked write-capable repo credential, you could [enable commit signature verification](https://argo-cd.readthedocs.io/en/stable/user-guide/gpg-verification/#enforcing-signature-verification). Even if someone could push a malicious commit, the commit would not by synced.\n\nYou should also enforce least privileges in Argo CD RBAC. Make sure users only have `repositories, update`, `applications, update`, or `applications, create` access if they absolutely need it.\n\n### References\n\n* The problem was initially reported in a [GitHub issue](https://github.com/argoproj/argo-cd/issues/12309)\n* [Argo CD RBAC configuration documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/)\n\n### For more information\n\n* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)\n* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd\n","state":0,"publishedAt":"2023-02-08T22:37:10+00:00","modifiedAt":"2026-09-10T03:50:07.8671787+00:00","affected":[{"ecosystem":"Go","name":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"2.6.0-rc1"},{"kind":"fixed","version":"2.6.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw","https://nvd.nist.gov/vuln/detail/CVE-2023-25163","https://github.com/argoproj/argo-cd/issues/12309","https://github.com/argoproj/argo-cd/pull/12320","https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac","https://github.com/argoproj/argo-cd","https://pkg.go.dev/vuln/GO-2023-1548"],"sourceUrl":"https://github.com/advisories/GHSA-mv6w-j4xc-qpfw","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-mv6w-j4xc-qpfw","identifiers":["GHSA-mv6w-j4xc-qpfw","BIT-argo-cd-2023-25163","CVE-2023-25163","GO-2023-1548"]},"retained":false,"historicalAffected":[]},{"revision":"5a2aa64be3b343928558451c82489046","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2023-1548","aliases":["BIT-argo-cd-2023-25163","CVE-2023-25163","GHSA-mv6w-j4xc-qpfw"],"title":"Repository access credential leak in github.com/argoproj/argo-cd/v2","description":"Argo CD has an output sanitization bug which leaks repository access credentials in error messages.\n\nThese error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI).\n\nThe user must have \"applications, create\" or \"applications, update\" RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository.\n\nIf the user has \"repositories, update\" access, they may edit an existing repository to introduce a URL typo or otherwise force an error message.","state":0,"publishedAt":"2023-02-15T16:43:39+00:00","modifiedAt":"2024-05-20T16:03:47+00:00","affected":[{"ecosystem":"Go","name":"github.com/argoproj/argo-cd/v2","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"2.6.0-rc1"},{"kind":"fixed","version":"2.6.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw","https://github.com/argoproj/argo-cd/issues/12309","https://github.com/argoproj/argo-cd/pull/12320"],"sourceUrl":"https://osv.dev/vulnerability/GO-2023-1548","license":"OSV · upstream source license applies","key":"osv:GO-2023-1548","identifiers":["GO-2023-1548","BIT-argo-cd-2023-25163","CVE-2023-25163","GHSA-mv6w-j4xc-qpfw"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-16T20:47:33.7814927+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T20:47:33.7814927+00:00","lastSuccessAt":"2026-11-16T20:47:33.9366168+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:47:33.9366175+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-6ce798019303d4cca0cf969df54ebcd3cc1a83b1a08848383be8acc935af42f1","complete":true,"records":426155,"lastAttemptAt":"2026-11-16T20:44:58.0469882+00:00","lastSuccessAt":"2026-11-16T20:44:57.4996638+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:44:58.0469882+00:00","snapshotPublishedAt":"2026-11-16T20:23:45+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-f07cbea7dec4426c9e098dc06e262653","complete":true,"records":13831,"lastAttemptAt":"2026-11-16T20:48:05.5360019+00:00","lastSuccessAt":"2026-11-16T20:48:05.528+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:48:05.528+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13884,"expectedIdentifiers":13884,"failedIdentifiers":0},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-16T20:47:33.7814927+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T20:47:33.7814927+00:00","lastSuccessAt":"2026-11-16T20:47:33.937464+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:47:33.9374641+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-1fe803c69f4440e590c33dfd73059c56","complete":false,"records":13843,"lastAttemptAt":"2026-11-16T20:48:01.3011684+00:00","lastSuccessAt":"2026-11-16T20:48:01.291+00:00","error":"110 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T20:48:01.291+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13374,"expectedIdentifiers":13884,"failedIdentifiers":110},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T20:47:33.7241651+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:47:33.7241651+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-16T20:44:58.1032592+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:44:58.1032592+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T20:47:33.7486021+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:47:33.7486021+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-d3135f0ae820c85dd153afd7ef11f8856f87d0924652a66bf0a06179e07249db","complete":true,"records":232552,"lastAttemptAt":"2026-11-16T20:47:33.5665375+00:00","lastSuccessAt":"2026-11-16T20:47:32.4854972+00:00","error":null,"lastVerifiedAt":"2026-11-16T20:47:33.5665375+00:00","snapshotPublishedAt":"2026-11-16T20:33:36+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}