SEPTEMBER 8, 2026
Live Feed
Back to database
Case File

CVE-2026-54526

CRITICAL · CVSS 9.9 EPSS 0.36% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-07-16 · Last synced 2026-08-15

CyberRota Analysis

AI-Generated

Argo Workflows versions prior to 3.7.15 and 4.0.6 are vulnerable due to an incomplete allow-list fix that permits users to inject arbitrary strategic merge patches into the artifact-GC pod, potentially allowing for the execution of malicious commands and the use of privileged resources. This critical vulnerability can lead to severe security breaches, including unauthorized access to host systems. Organizations using affected versions of Argo Workflows should prioritize immediate upgrades to mitigate this risk.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-54526
Severity
CRITICAL
CVSS
9.9
EPSS
0.36%
Kubernetes

Original NVD Description

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection, and WorkflowSpec.ArtifactGC is allow-listed wholesale; the struct behind that field, WorkflowLevelArtifactGC, has a PodSpecPatch sub-field whose contents flow unmodified into util.ApplyPodSpecPatch on the artifact-GC pod, the same sink the original fix closed for WorkflowSpec.PodSpecPatch, so a user submitting a Workflow under templateReferencing: Strict or Secure (against a referenced WorkflowTemplate that declares an output artifact and setting spec.artifactGC.strategy: OnWorkflowCompletion) can still inject an arbitrary strategic merge patch into the artifact-GC pod, including hostPath volumes, privileged: true, arbitrary image and command, and hostNetwork: true, defeating the stated purpose of Strict/Secure reference mode. This issue is fixed in versions 3.7.15 and 4.0.6.

Related CVEs

Other vulnerabilities affecting the same vendor(s)