Vulnerabilities / CVE-2026-54526

critical

CVE-2026-54526

Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892)

Published Modified CWE 284
In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GHSA8.9CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H
Bitnami10.0CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Trivy's own label is CRITICAL. Rated critical by NVD, Bitnami. Rated lower by GHSA (high).

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.

Affected packages and fixed versions

SourcePackageFixed in
bitnami::Bitnami Vulnerability Databaseargo-workflows3.7.15, 4.0.6
chainguardkubeflow-pipelines, kubeflow-pipelines-driver-fips, kubeflow-pipelines-fips2.17.2-r4 and 2 more
go::GitHub Security Advisory Gogithub.com/argoproj/argo-workflows, github.com/argoproj/argo-workflows/v3, github.com/argoproj/argo-workflows/v43.7.15 and 1 more
minimosargo-workflow-controller-3.7, argo-workflow-controller-4.0, argo-workflow-controller-fips-3.7 and 9 more3.7.15-r0 and 1 more
wolfikubeflow-pipelines2.17.2-r4
Show all 20 entries from 5 sources
SourcePackageFixed in
bitnami::Bitnami Vulnerability Databaseargo-workflows3.7.15, 4.0.6
chainguardkubeflow-pipelines2.17.2-r4
chainguardkubeflow-pipelines-driver-fips2.17.0-r5
chainguardkubeflow-pipelines-fips2.17.0-r9
go::GitHub Security Advisory Gogithub.com/argoproj/argo-workflowsno fix listed
go::GitHub Security Advisory Gogithub.com/argoproj/argo-workflows/v33.7.15
go::GitHub Security Advisory Gogithub.com/argoproj/argo-workflows/v44.0.6
minimosargo-workflow-controller-3.73.7.15-r0
minimosargo-workflow-controller-4.04.0.6-r0
minimosargo-workflow-controller-fips-3.73.7.15-r0
minimosargo-workflow-controller-fips-4.04.0.6-r0
minimosargo-workflow-executor-3.73.7.15-r0
minimosargo-workflow-executor-4.04.0.6-r0
minimosargo-workflow-executor-fips-3.73.7.15-r0
minimosargo-workflow-executor-fips-4.04.0.6-r0
minimosargo-workflows-3.73.7.15-r0
minimosargo-workflows-4.04.0.6-r0
minimosargo-workflows-fips-3.73.7.15-r0
minimosargo-workflows-fips-4.04.0.6-r0
wolfikubeflow-pipelines2.17.2-r4

References

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.