{"answers":{"affected":"6 open source packages ship an affected version, including github.com/argoproj/argo-cd and github.com/argoproj/argo-cd/v2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-40026 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-40026 is a medium-severity vulnerability in Argoproj Argo Cd, published on 27 Sep 2023."},"fix_prompt":"Check this codebase for CVE-2023-40026 and fix it if it is affected.\n\nWhat it is: CVE-2023-40026 is a medium-severity vulnerability in Argoproj Argo Cd, published on 27 Sep 2023. \nExploitation: There is no known exploitation of CVE-2023-40026 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/argoproj/argo-cd (Go): affected all versions; no fix listed\n- github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; no fix listed\n- github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; no fix listed\n- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.3.0\n- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.3.0\n- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.3.0\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-40026/ (Markdown: https://insights.sbomify.com/CVE-2023-40026/index.md)","id":"CVE-2023-40026","markdown":"https://insights.sbomify.com/CVE-2023-40026/index.md","name":"CVE-2023-40026","record":{"aliases":["GHSA-6jqw-jwf5-rp8h","GO-2023-2085"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"argo_cd","vendor":"argoproj"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Argo CD is a declarative continuous deployment framework for Kubernetes. In Argo CD versions prior to 2.3 (starting at least in v0.1.0, but likely in any version using Helm before 2.3), using a specifically-crafted Helm file could reference external Helm charts handled by the same repo-server to leak values, or files from the referenced Helm Chart. This was possible because Helm paths were predictable. The vulnerability worked by adding a Helm chart that referenced Helm resources from predictable paths. Because the paths of Helm charts were predictable and available on an instance of repo-server, it was possible to reference and then render the values and resources from other existing Helm charts regardless of permissions. While generally, secrets are not stored in these files, it was nevertheless possible to reference any values from these charts. This issue was fixed in Argo CD 2.3 and subsequent versions by randomizing Helm paths. User's still using Argo CD 2.3 or below are advised to update to a supported version. If this is not possible, disabling Helm chart rendering, or using an additional repo-server for each Helm chart would prevent possible exploitation.","ecosystems":["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":"Path traversal allows leaking out-of-bound Helm charts from Argo CD repo-server","id":"CVE-2023-40026","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":"argoproj:argo_cd","products":["argoproj:argo_cd"],"type":null,"year":"2023"},"n_packages":6,"n_references":2,"next":{"headline":"Conditionally missing authorization in @keystone-6/core","id":"CVE-2023-40027"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-cd","purl":"pkg:golang/github.com/argoproj/argo-cd","source":"GO-2023-2085"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["1.8.7"],"package":"github.com/argoproj/argo-cd","purl":null,"source":"GHSA-6jqw-jwf5-rp8h"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["1.8.7"],"package":"github.com/argoproj/argo-cd","purl":"pkg:golang/github.com/argoproj/argo-cd","source":"GHSA-6jqw-jwf5-rp8h"},{"ecosystem":"Go","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-cd/v2","purl":null,"source":"GHSA-6jqw-jwf5-rp8h"},{"ecosystem":"Go","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-cd/v2","purl":"pkg:golang/github.com/argoproj/argo-cd/v2","source":"GHSA-6jqw-jwf5-rp8h"},{"ecosystem":"Go","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"github.com/argoproj/argo-cd/v2","purl":"pkg:golang/github.com/argoproj/argo-cd/v2","source":"GO-2023-2085"}],"prev":{"headline":"Argo CD web terminal session doesn't expire","id":"CVE-2023-40025"},"products":["argo-cd"],"published":"2023-09-27","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":"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":"2024-09-20","vendors":["argoproj"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2023-40026/"}