# CVE-2023-50726: Users with `create` but not `override` privileges can perform local sync in argo-cd > Users with create but not override privileges can bypass source restrictions to sync local manifests in Argo CD. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Mar 2024 - **Updated:** 15 Apr 2025 - **Also known as:** BIT-argo-cd-2023-50726, GHSA-g623-jcgg-mhmm, GO-2024-2643 ## What is CVE-2023-50726? CVE-2023-50726 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have `create` privileges but not `override` privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is not enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. The bug has been patched in Argo CD versions 2.10.3, 2.9.8, and 2.8.12. Users are advised to upgrade. Users unable to upgrade may mitigate the risk of branch protection bypass by removing `applications, create` RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version. Weakness: CWE-863 (Incorrect Authorization), CWE-269 (Improper Privilege Management) ## Which versions are affected by CVE-2023-50726? 11 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0 | 2.8.12, 2.9.8, 2.10.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc3 | 2.8.12 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc3 | 2.8.12 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | 2.10.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0 | 2.10.3 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0 | 2.9.8 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0 | 2.9.8 | | `argo-cd` | Bitnami | From 1.2.0 | 2.8.12, 2.9.8, 2.10.3 | | `github.com/argoproj/argo-cd` | Go | From 1.2.0-rc1 | None | | `github.com/argoproj/argo-cd` | Go | From 1.2.0-rc1 to 1.8.7 | None | | `github.com/argoproj/argo-cd` | Go | From 1.2.0-rc1 to 1.8.7 | None | Products: Argoproj Argo Cd. ## How do I fix CVE-2023-50726? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.8.12, 2.9.8 or 2.10.3. ## Is CVE-2023-50726 being exploited? There is no known exploitation of CVE-2023-50726 in the wild and no public exploit code. ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-50726 and fix it if it is affected. What it is: CVE-2023-50726 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-50726 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0; fixed in 2.8.12, 2.9.8, 2.10.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-rc3; fixed in 2.8.12 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-rc3; fixed in 2.8.12 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; fixed in 2.10.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0; fixed in 2.10.3 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0; fixed in 2.9.8 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0; fixed in 2.9.8 - argo-cd (Bitnami): affected from 1.2.0; fixed in 2.8.12, 2.9.8, 2.10.3 - github.com/argoproj/argo-cd (Go): affected from 1.2.0-rc1; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.2.0-rc1 up to 1.8.7; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.2.0-rc1 up to 1.8.7; no fix listed Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-50726/ (Markdown: https://insights.sbomify.com/CVE-2023-50726/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-50726 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-50726 - OSV: https://osv.dev/vulnerability/CVE-2023-50726 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-50726/ Summaries are generated and may contain mistakes; the official description above is the record.