Loading story…
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.
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.
Argo Workflows v3.7.14 and v4.0.5 were identified as the patched versions that fully resolve CVE-2026-40886, a denial-of-service issue caused by unchecked annotation parsing.
Tekton Pipelines 1.11.1 or later was identified as the definitive fix for CVE-2026-40923, adding filepath.Clean path normalization logic to admission webhooks to prevent VolumeMount path restriction bypass.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcecvereports.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.
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.
Jul 17, 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
Researchers disclosed an **unpatched unauthenticated remote code execution flaw** in Argo CD’s `repo-server` that can be exploited through the gRPC `GenerateManifest` endpoint when attackers can reach the internal service port. The attack chain abuses Argo CD’s handling of Kustomize options, allowing a crafted request to pass attacker-controlled settings such as `--enable-helm` and `--helm-command` so code from a malicious Git repository is executed on the repo-server host. Synacktiv said it reported the issue to Argo CD maintainers in January 2025, but no patch or CVE had been issued at the time of disclosure. After achieving code execution, the researchers demonstrated theft of the `REDIS_PASSWORD` environment variable and poisoning of Argo CD’s Redis-backed cache to force deployment of attacker-controlled manifests on the next sync, creating a path to **full Kubernetes cluster compromise**. The reported mitigation is to enforce Kubernetes network policies that restrict access to `repo-server` and Redis to trusted Argo CD components, as those protections are not enabled by default in common Helm-based deployments.
Jul 12, 2026