Argo Workflows: Unchecked annotation parsing in pod informer crashes Argo Workflows Controller
CVE-2026-40886GHSA-5jv8-h7qh-rf5p
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/argoproj/argo-workflows/v4
- Affected
- >= 4.0.0, < 4.0.5
- Fixed in
- 4.0.5
Go github.com/argoproj/argo-workflows/v3
- Affected
- >= 3.7.0, < 3.7.14>= 3.6.5, <= 3.6.19
- Fixed in
- 3.7.14
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5jv8-h7qh-rf5p lists affected ranges: Go github.com/argoproj/argo-workflows/v4 >=4.0.0 =3.7.0 =3.6.5 <=3.6.19
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
- EPSS
- CVE-2026-40886: 0.38% estimated exploitation activity in the next 30 days; percentile 31.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An unchecked array index in the pod informer's podGCFromPod() function causes a controller-wide panic when a workflow pod carries a malformed workflows.argoproj.io/pod-gc-strategy annotation. Because the panic occurs inside an informer goroutine (outside the controller's recover() scope), it crashes the entire controller process. The poisoned pod persists across restarts, causing a crash loop that halts all workflow processing until the pod is manually deleted. Details podGCFromPod() splits the annotation value on "/" and unconditionally accesses parts[1]: If the annotation value contains no "/", parts has length 1 and parts[1] panics with index out of range. The code was introduced in #14129 and affects versions: - 3.6.x: v3.6.5 through v3.6.19 (backport in #14263) - 3.7.x: v3.7.0-rc1 through v3.7.12 - 4.x: v4.0.0-rc1 through v4.0.3 - Not affected: v3.6.4 and earlier PoC Apply this workflow to a cluster running the Argo Workflows controller: Within seconds the controller…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-5jv8-h7qh-rf5p
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-40886 Advisory: Argo Workflows: Unchecked annotation parsing in pod informer crashes Argo Workflows Controller IDs: CVE-2026-40886, GHSA-5jv8-h7qh-rf5p Record: https://patchnext.com/advisories/cve-2026-40886 (revision 1, source checked 26 Oct 2026, 15:19 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-workflows/v4 4.0.5; github.com/argoproj/argo-workflows/v3 3.7.14. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/argoproj/argo-workflows/v4: affected >= 4.0.0, < 4.0.5; fixed in 4.0.5 - Go github.com/argoproj/argo-workflows/v3: affected >= 3.7.0, < 3.7.14; >= 3.6.5, <= 3.6.19; fixed in 3.7.14 ## Suggested inspection (read-only) - Go github.com/argoproj/argo-workflows/v4: check the installed version with your package manager. - Go github.com/argoproj/argo-workflows/v3: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/argoproj/argo-workflows/v4, github.com/argoproj/argo-workflows/v3. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-5jv8-h7qh-rf5p (GitHub-reviewed advisory GHSA-5jv8-h7qh-rf5p lists affected ranges: Go github.com/argoproj/argo-workflows/v4 >=4.0.0 =3.7.0 =3.6.5 <=3.6.19) Commands are suggestions: review each one before running it.
Loading voting…