Approved changes feed: RSS · Atom
cpe:2.3:a:argoproj:argo-helm:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Argoproj (b84a6b2f-3264-516e-b963-717ce37bd8b9) |
|---|---|
| Product | Argo Helm (a47b0a26-6567-544c-b196-89a206d82d38) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-62185 |
vulnerable | 2026-07-29 01:06:18.982253 |
Argo CD Helm Chart < 10.0.0 Missing Network Policy RCE
HIGH (7.6)
Argo CD Helm Chart before 10.0.0 fails to install network policies by default, allowing any pod on a cluster to access repo-server and other Argo APIs. Attackers can exploit this unrestricted network access through combined attacks to achieve cluster compromise and remote code execution.
Published: 2026-07-13T21:31:23.660Z
Updated: 2026-07-14T22:03:46.962Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-15416 |
vulnerable | 2026-07-29 00:26:18.091460 |
Argo-cd: argo cd unauthenticated remote code execution in repo-server via generatemanifest grpc endpoint
HIGH (8.9)
A flaw was identified in Argo CD, the GitOps engine used by Red Hat OpenShift GitOps, that could allow an unauthenticated attacker with network access to the Argo CD repo-server to achieve remote code execution. Under certain conditions, the attacker may then manipulate cached data to deploy malicious Kubernetes resources to managed clusters, potentially resulting in complete cluster compromise.
Published: 2026-07-14T08:56:29.942Z
Updated: 2026-08-11T00:38:39.224Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52814 |
vulnerable | 2026-06-08 06:52:16.273342 |
Helm Lacks Granularity in Workflow Role
LOW (2.8)
Argo Helm is a collection of community maintained charts for `argoproj.github.io` projects. Prior to version 0.45.0, the `workflow-role`) lacks granularity in its privileges, giving permissions to `workflowtasksets` and `workflowartifactgctasks` to all workflow Pods, when only certain types of Pods created by the Controller require these privileges. The impact is minimal, as an attack could only affect status reporting for certain types of Pods and templates. Version 0.45.0 fixes the issue.
Published: 2024-11-22T15:53:06.238Z
Updated: 2024-11-22T17:25:26.112Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52799 |
vulnerable | 2026-06-08 06:52:16.255006 |
Argo Workflows Chart: Excessive Privileges in Workflow Role
HIGH (8.3)
Argo Workflows Chart is used to set up argo and its needed dependencies through one command. Prior to 0.44.0, the workflow-role has excessive privileges, the worst being create pods/exec, which will allow kubectl exec into any Pod in the same namespace, i.e. arbitrary code execution within those Pods. If a user can be made to run a malicious template, their whole namespace can be compromised. This affects versions of the argo-workflows Chart that use appVersion: 3.4 and above, which no longer need these permissions for the only available Executor, Emissary. It could also affect users below 3.4 depending on their choice of Executor in those versions. This only affects the Helm Chart and not the upstream manifests. This vulnerability is fixed in 0.44.0.
Published: 2024-11-21T17:02:01.525Z
Updated: 2024-11-21T20:48:51.507Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.