Advisory record · GHSA-5jv8-h7qh-rf5p

Argo Workflows: Unchecked annotation parsing in pod informer crashes Argo Workflows Controller

CVSS 7.7 HighEPSS 0.0038 · 31st percentile

Published by the GitHub Advisory Database at 23 Apr 2026, 21:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/argoproj/argo-workflows/v4Go>=4.0.0, <4.0.54.0.5
github.com/argoproj/argo-workflows/v3Go>=3.7.0, <3.7.14 || >=3.6.5, <=3.6.193.7.14
Identifiers
GHSA-5jv8-h7qh-rf5p · BIT-argo-workflows-2026-40886 · CVE-2026-40886 · GO-2026-5148
Weakness (CWE)
CWE-129 · CWE-1285
Published
23 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Argo Workflows versions 4.0.0 through 4.0.4 and 3.6.5 through 3.6.19, plus 3.7.0 through 3.7.13, are affected. A user with permission to create Workflow resources can submit a pod with a malformed pod-gc-strategy annotation that makes the controller panic and crash repeatedly, halting all workflow processing until the poisoned pod is deleted. Upgrade to 4.0.5 or 3.7.14; no workaround is listed.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.7 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 31st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.