8.6

CVE-2023-22736: argoproj argo_cd Missing Authorization

CVSS: 8.6v3.1HighModified
AliasesGHSA-6p4m-hw2h-6gmwGO-2023-1512
Published 26-01-2023Last modified 10-03-2025

Vulnerability summary

CVE-2023-22736 is a high (CVSS 8.6) Missing Authorization vulnerability in argoproj argo_cd. EPSS estimates a 0.78% chance of exploitation in the next 30 days, higher than 55.4% of scored vulnerabilities.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.6/10
010
High · v3.1 (CVE.org)
EPSS score
0.78%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 26-01-2023
    PublishedVulnerability first disclosed.
  2. 10-03-2025
    Last modifiedVulnerability information updated.

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions starting with 2.5.0-rc1 and above, prior to 2.5.8, and version 2.6.0-rc4, are vulnerable to an authorization bypass bug which allows a malicious Argo CD user to deploy Applications outside the configured allowed namespaces. Reconciled Application namespaces are specified as a comma-delimited list of glob patterns. When sharding is enabled on the Application controller, it does not enforce that list of patterns when reconciling Applications. For example, if Application namespaces are configured to be argocd-*, the Application controller may reconcile an Application installed in a namespace called other, even though it does not start with argocd-. Reconciliation of the out-of-bounds Application is only triggered when the Application is updated, so the attacker must be able to cause an update operation on the Application resource. This bug only applies to users who have explicitly enabled the "apps-in-any-namespace" feature by setting `application.namespaces` in the argocd-cmd-params-cm ConfigMap or otherwise setting the `--application-namespaces` flags on the Application controller and API server components. The apps-in-any-namespace feature is in beta as of this Security Advisory's publish date. The bug is also limited to Argo CD instances where sharding is enabled by increasing the `replicas` count for the Application controller. Finally, the AppProjects' `sourceNamespaces` field acts as a secondary check against this exploit. To cause reconciliation of an Application in an out-of-bounds namespace, an AppProject must be available which permits Applications in the out-of-bounds namespace. A patch for this vulnerability has been released in versions 2.5.8 and 2.6.0-rc5. As a workaround, running only one replica of the Application controller will prevent exploitation of this bug. Making sure all AppProjects' sourceNamespaces are restricted within the confines of the configured Application namespaces will also prevent exploitation of this bug.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.78%

Chance of exploitation in the next 30 days

Percentile

55%

Versus all other CVEs

30-day change

0.00 pp

From 0.78% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.78%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Argoproj2 products
  • argo_cdEOL≥ 2.5.0, < 2.5.8 | 2.6.0:rc1 | 2.6.0:rc2 | 2.6.0:rc3 | 2.6.0:rc4
  • argo-cd≥ 2.5.0=rc1, < 2.5.8 | = 2.6.0-rc4, < 2.6.0-rc5
Github.com/argoproj1 product
  • argo-cdAll versions (No fix recorded)
Github.com/argoproj/argo-cd1 product
  • v2≥ 2.5.0-rc1, < 2.5.8 | ≥ 2.6.0-rc4, < 2.6.0-rc5

3 vendors · 4 products

References

3 links