Loading story…
Argo Workflows patched CVE-2026-54526, a privilege-escalation flaw that lets a user bypass Strict and Secure workflowTemplateRef protections through the allow-listed WorkflowSpec.ArtifactGC field. The issue stems from an incomplete fix for CVE-2026-31892: validation only checked top-level WorkflowSpec fields, while nested ArtifactGC settings such as podSpecPatch, serviceAccountName, and podMetadata could still reach the artifact garbage-collection pod unsanitized. In affected deployments, an attacker able to submit a Workflow referencing a hardened WorkflowTemplate could inject a strategic merge patch into the artifact-GC pod when output artifacts and OnWorkflowCompletion cleanup were in use.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-54526 was disclosed as an incomplete fix for CVE-2026-31892 in Argo Workflows, allowing bypass of Strict and Secure template reference protections through WorkflowSpec.ArtifactGC.PodSpecPatch. The disclosure states the issue is fixed in Argo Workflows versions 3.7.15 and 4.0.6.
On June 10, 2026, Argo Workflows merged commits fixing a privilege-escalation issue in Strict/Secure workflowTemplateRef mode where nested ArtifactGC fields such as podSpecPatch, serviceAccountName, and podMetadata could be used to control the artifact-GC pod. The patch updated validation and sanitization logic to block or strip those sensitive nested fields while preserving benign ArtifactGC settings.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two newly reported Kubernetes CI/CD vulnerabilities affect **Tekton Pipelines** and **Argo Workflows**, with both issues tied to insufficient validation of user-supplied fields in cluster workflow objects. **CVE-2026-40923** allows a `VolumeMount.mountPath` path restriction bypass in Tekton Pipelines because admission webhooks failed to normalize paths, enabling traversal patterns such as `..`; the fix is to upgrade to **Tekton Pipelines 1.11.1 or later**, which adds `filepath.Clean` logic. **CVE-2026-40886** causes a denial of service in Argo Workflows through unchecked parsing of the `workflows.argoproj.io/pod-gc-strategy` annotation, and is fully patched in **Argo Workflows 3.7.14** and **4.0.5**. Where upgrades cannot be applied immediately, defenders are advised to enforce **Kubernetes admission policies** using **OPA Gatekeeper**, **Kyverno**, or native validating controls to block malicious Tekton `Task` and `TaskRun` requests and to validate incoming Argo `Workflow` annotations. The guidance also calls for tightening **RBAC** so only trusted CI/CD service accounts and authorized personnel can create Tekton resources, restricting namespace access to limit blast radius, and, in Argo environments already forced into a controller crash loop, manually deleting the malicious `Workflow` object from the Kubernetes API so the controller can recover.
Jun 29, 2026
A high-severity flaw tracked as **CVE-2026-15416** allows unauthenticated remote code execution in **Argo CD** by abusing the repo-server's `GenerateManifest` gRPC endpoint. According to Red Hat and related disclosures, an attacker with network access to the repo-server interface can exploit malicious `KustomizeOptions`, including `BuildOptions` or `BinaryPath`, to run arbitrary commands inside the repo-server pod. The issue is rated **CVSS 8.9** and mapped to **CWE-306** for missing authentication on a critical function. The vulnerability can also be chained with access to the Argo CD **Redis** cache to tamper with cached data and push attacker-controlled Kubernetes manifests to Argo CD-managed environments, creating a path to full cluster compromise. Red Hat said affected products include Argo CD deployments and related OpenShift components, while **OpenShift GitOps 1.20 and 1.21** are not affected because default Kubernetes `NetworkPolicy` settings block the required access to internal repo-server and Redis services. Recommended actions include patching to a fixed version, preventing external exposure of the repo-server, restricting network access to the gRPC endpoint and Redis, and reviewing deployment configurations.
Jul 15, 2026
A critical flaw in Argo CD, tracked as **`CVE-2026-43824`**, exposed plaintext Kubernetes Secrets to low-privileged authenticated users through the `ServerSideDiff` endpoint. The vulnerability was caused by missing authorization and secret-masking protections, allowing the endpoint to return raw `PredictedLive` and `NormalizedLive` data from the Kubernetes API without applying Argo CD’s normal `hideSecretData()` masking. As a result, users with application `get` access could retrieve sensitive values including service account tokens, TLS material, database credentials, and API keys. The risk was heightened when an Application used the annotation `argocd.argoproj.io/compare-options: IncludeMutationWebhook=true`, which bypassed an additional sanitization step and made secret extraction especially effective for resources influenced by mutation webhooks. The issue affected Argo CD versions **3.2.0 through 3.3.8**, and maintainers released fixes in **3.2.11** and **3.3.9**. Administrators were urged to upgrade, tighten RBAC permissions, remove the risky annotation where possible, and review Argo CD API logs for suspicious `ServerSideDiff` activity.
Jun 29, 2026