Argo CD' API server does not enforce project sourceNamespaces
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The API server does not enforce project sourceNamespaces which allows attackers to use the UI to edit resources which should only be mutable via gitops. This vulenrability is fixed in 2.10.7, 2.9.12, and 2.8.16.
- Published
- Apr 15, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-863
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.3
- CNA · GitHub_M
- 4.8
- 1.5 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| argoproj | argo cd | cpe:2.3:a:argoproj:argo_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.4.0 and later · before 2.8.16
- argoproj argo cd2.9.0 and later · before 2.9.12
- argoproj argo cd2.10.0 and later · before 2.10.7
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.10.0, < 2.10.7, >= 2.9.0, < 2.9.12, >= 2.4.0, < 2.8.16affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/argoproj/argo-cd | all versions | — |
| Go | github.com/argoproj/argo-cd/v2 | from 2.10.0 · before 2.10.7 | 2.10.7 |
| Go | github.com/argoproj/argo-cd/v2 | from 2.4.0 · before 2.8.16 | 2.8.16 |
| Go | github.com/argoproj/argo-cd/v2 | from 2.9.0 · before 2.9.12 | 2.9.12 |
Same product
argoproj: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-55190Argo CD: Project API Token Exposes Repository Credentials41Plan
- CVE-2022-29165Argo CD will blindly trust JWT claims if anonymous access is enabled41Plan
- CVE-2024-21652Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss39Monitor
- CVE-2026-42880ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction38Monitor
- CVE-2023-40029Cluster secret might leak in cluster details page in Argo CD38Monitor
- CVE-2022-31105Argo CD's certificate verification is skipped for connections to OIDC providers38Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| argoproj argo-cd | 2.10.7 · description | Vendor (CNA) |
| Go:github.com/argoproj/argo-cd/v2 | 2.10.7 | Package registry (OSV) |
| Go:github.com/argoproj/argo-cd/v2 | 2.8.16 | Package registry (OSV) |
| Go:github.com/argoproj/argo-cd/v2 | 2.9.12 | Package 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.
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 researchersFinders, 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.
- CVE-2023-22482445 days apartJWT audience claim is not verified35Monitor
- CVE-2023-23947424 days apartArgo CD users with any cluster secret update access may update out-of-bounds cluster secrets34Monitor
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/argoproj/argo-cd/commit/c514105af739eebedb9dbe89d8a6dd8dfc30bb2c
- github.com/argoproj/argo-cd/commit/c5a252c4cc260e240e2074794aedb861d07e9ca5
- github.com/argoproj/argo-cd/commit/e0ff56d89fbd7d066e9c862b30337f6520f13f17
- github.com/argoproj/argo-cd/security/advisories/GHSA-2gvw-w6fj-7m3c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.