Argo Workflows (controller pod informer, pod-gc-strategy annotation parsing): A malformed

Impact

A malformed workflows.argoproj.io/pod-gc-strategy annotation makes the pod informer index past the end of a split, and the panic happens in an informer goroutine outside the controller's recover, killing the whole process. The poisoned pod survives restarts, so the controller crash-loops and every tenant's workflow scheduling stops until an operator manually finds and deletes that one pod.

Who can reach it

Anyone who can create or annotate a pod in a namespace the controller watches - which includes any tenant with normal pod-create rights, not just workflow submitters.

What to do

Upgrade the controller to 3.7.14 or 4.0.5 and restart it. To recover a cluster already in the crash loop, find the pod carrying the malformed annotation and delete it before or during the upgrade, otherwise the new controller crashes on the same object.

References

Related entries

• RHACM multicloud-operators-channel: managed-cluster agent reads all Secrets in hub Channel namespacesCVE-2026-73122 · Red Hat Advanced Cluster Management multicloud-operators-channel (hub subscription controller)High
• RHACM subscription controller: HelmRelease secretRef.Namespace reads Secrets from any namespaceCVE-2026-73137 · Red Hat Advanced Cluster Management multicloud-operators-subscription (HelmRelease secretRef)High
• RHACS Central: unbounded GraphQL query depth lets an authenticated user stall the management planeCVE-2026-9165 · Red Hat Advanced Cluster Security for Kubernetes (Central GraphQL API, query depth limit)High
• KubeVirt: Symlink path traversal in the virt-exportserver VMExport directory endpointCVE-2026-9804 · KubeVirtHigh
• ingress-nginx: Custom nginx snippets in an Ingress annotation retrieve the ingress-nginx service-account tokenCVE-2021-25742 · ingress-nginxHigh
• ingress-nginx: Ingress `path` can be pointed at the service-account token fileCVE-2021-25745 · ingress-nginxHigh