{"answers":{"affected":"4 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and argo-cd. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25163 in the wild and no public exploit code.","fix":"Upgrade github.com/argoproj/argo-cd/v2 to 2.6.1 or later.","what":"CVE-2023-25163 is a medium-severity vulnerability in Argoproj Argo Cd, published on 8 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-25163 and fix it if it is affected.\n\nWhat it is: CVE-2023-25163 is a medium-severity vulnerability in Argoproj Argo Cd, published on 8 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-25163 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/argoproj/argo-cd/v2 (Go): affected from 2.6.0-rc1; fixed in 2.6.1\n- github.com/argoproj/argo-cd/v2 (Go): affected from 2.6.0-rc1; fixed in 2.6.1\n- github.com/argoproj/argo-cd/v2 (Go): affected from 2.6.0-rc1; fixed in 2.6.1\n- argo-cd (Bitnami): affected from 2.6.0 up to 2.6.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-25163/ (Markdown: https://insights.sbomify.com/CVE-2023-25163/index.md)","id":"CVE-2023-25163","markdown":"https://insights.sbomify.com/CVE-2023-25163/index.md","name":"CVE-2023-25163","record":{"aliases":["BIT-argo-cd-2023-25163","GHSA-mv6w-j4xc-qpfw","GO-2023-1548"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes GitOps tool","requires_auth":"low_privilege","summary":"Attackers with application creation or update permissions can view repository credentials leaked in error messages and logs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"argo_cd","vendor":"argoproj"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":["Bitnami","Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Argo CD leaks repository credentials in user-facing error messages and in logs","id":"CVE-2023-25163","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"argoproj:argo_cd","products":["argoproj:argo_cd"],"type":"information_disclosure","year":"2023"},"n_packages":4,"n_references":4,"next":{"headline":"Sensitive Information leak via Script File in TinaCMS","id":"CVE-2023-25164"},"packages":[{"ecosystem":"Bitnami","fixed":[],"introduced":["2.6.0","2.6.0-rc1","2.6.0-rc2","2.6.0-rc3","2.6.0-rc4","2.6.0-rc5","2.6.0-rc6","2.6.0-rc7"],"last_affected":["2.6.0","2.6.0-rc1","2.6.0-rc2","2.6.0-rc3","2.6.0-rc4","2.6.0-rc5","2.6.0-rc6","2.6.0-rc7"],"package":"argo-cd","purl":"pkg:bitnami/argo-cd","source":"BIT-argo-cd-2023-25163"},{"ecosystem":"Go","fixed":["2.6.1"],"introduced":["2.6.0-rc1"],"last_affected":[],"package":"github.com/argoproj/argo-cd/v2","purl":null,"source":"GHSA-mv6w-j4xc-qpfw"},{"ecosystem":"Go","fixed":["2.6.1"],"introduced":["2.6.0-rc1"],"last_affected":[],"package":"github.com/argoproj/argo-cd/v2","purl":"pkg:golang/github.com/argoproj/argo-cd/v2","source":"GHSA-mv6w-j4xc-qpfw"},{"ecosystem":"Go","fixed":["2.6.1"],"introduced":["2.6.0-rc1"],"last_affected":[],"package":"github.com/argoproj/argo-cd/v2","purl":"pkg:golang/github.com/argoproj/argo-cd/v2","source":"GO-2023-1548"}],"prev":{"headline":"Nextcloud Server vulnerable to SSRF via filter bypass due to lax checking on IPs","id":"CVE-2023-25162"},"products":["argo-cd"],"published":"2023-02-08","related":[{"cvss_score":10,"headline":"Argo CD: Project API Token Exposes Repository Credentials","id":"CVE-2025-55190","kev_date_added":null,"published":"2025-09-04"},{"cvss_score":10,"headline":"Argo CD will blindly trust JWT claims if anonymous access is enabled","id":"CVE-2022-29165","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":9.9,"headline":"Cluster secret might leak in cluster details page in Argo CD","id":"CVE-2023-40029","kev_date_added":null,"published":"2023-09-07"},{"cvss_score":9.9,"headline":"Improper access control allows admin privilege escalation in Argo CD","id":"CVE-2022-24768","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":9.8,"headline":"Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss","id":"CVE-2024-21652","kev_date_added":null,"published":"2024-03-18"},{"cvss_score":9.6,"headline":"ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction","id":"CVE-2026-42880","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":9.1,"headline":"Argo CD allows cross-site scripting on repositories page","id":"CVE-2025-47933","kev_date_added":null,"published":"2025-05-29"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["argoproj"]},"summary":"Attackers with application creation or update permissions can view repository credentials leaked in error messages and logs.","url":"https://insights.sbomify.com/CVE-2023-25163/"}