Skip to content
Noroxi
CVE-2023-23947· NVD / CVE Program· CNA GitHub_M

Argo CD users with any cluster secret update access may update out-of-bounds cluster secrets

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All Argo CD versions starting with 2.3.0-rc1 and prior to 2.3.17, 2.4.23 2.5.11, and 2.6.2 are vulnerable to an improper authorization bug which allows users who have the ability to update at least one cluster secret to update any cluster secret. The attacker could use this access to escalate privileges (potentially controlling Kubernetes resources) or to break Argo CD functionality (by preventing connections to external clusters). A patch for this vulnerability has been released in Argo CD versions 2.6.2, 2.5.11, 2.4.23, and 2.3.17. Two workarounds are available. Either modify the RBAC configuration to completely revoke all `clusters, update` access, or use the `destinations` and `clusterResourceWhitelist` fields to apply similar restrictions as the `namespaces` and `clusterResources` fields.

HighCVSS 8.5 · v3.1—No exploit Fix available
Published
Feb 16, 2023
Updated
Jun 17, 2026
EPSS
0.7% · 50th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.5
CNA · GitHub_M
9.1
0.6 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
argoprojargo cd

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • argoproj argo cd2.3.0 and later · before 2.3.17
  • argoproj argo cd2.4.0 and later · before 2.4.23
  • argoproj argo cd2.5.0 and later · before 2.5.11
  • argoproj argo cd2.6.0 and later · before 2.6.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • argoproj argo-cd

    • >= 2.3.0-rc1, < 2.3.17, >= 2.4.0, < 2.4.23, >= 2.5.0, < 2.5.11, >= 2.6.0, < 2.6.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/argoproj/argo-cdfrom 2.3.0 · before 2.3.172.3.17
Gogithub.com/argoproj/argo-cdfrom 2.4.0 · before 2.4.232.4.23
Gogithub.com/argoproj/argo-cdfrom 2.5.0 · before 2.5.112.5.11
Gogithub.com/argoproj/argo-cdfrom 2.6.0 · before 2.6.22.6.2
Gogithub.com/argoproj/argo-cdall versions—
Gogithub.com/argoproj/argo-cd/v2from 2.3.0 · before 2.3.172.3.17
Gogithub.com/argoproj/argo-cd/v2from 2.4.0 · before 2.4.232.4.23
Gogithub.com/argoproj/argo-cd/v2from 2.5.0 · before 2.5.112.5.11
Gogithub.com/argoproj/argo-cd/v2from 2.6.0 · before 2.6.22.6.2

Same product

argoproj: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-55190Argo CD: Project API Token Exposes Repository Credentials
    41Plan
  • CVE-2022-29165Argo CD will blindly trust JWT claims if anonymous access is enabled
    41Plan
  • CVE-2024-21652Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
    39Monitor
  • CVE-2026-42880ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction
    38Monitor
  • CVE-2023-40029Cluster secret might leak in cluster details page in Argo CD
    38Monitor
  • CVE-2022-31105Argo CD's certificate verification is skipped for connections to OIDC providers
    38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/argoproj/argo-cd2.3.17Package registry (OSV)
Go:github.com/argoproj/argo-cd2.4.23Package registry (OSV)
Go:github.com/argoproj/argo-cd2.5.11Package registry (OSV)
Go:github.com/argoproj/argo-cd2.6.2Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.3.17Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.4.23Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.5.11Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.6.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records