Affects widely used Argo Workflows; public webhook endpoint; potential DoS could disrupt CI/CD pipelines across many orgs.
CVE-2026-42294
Memory exhaustion DoS via Argo Workflows webhook endpoint
Is CVE-2026-42294 being exploited?
Not confirmed. CVE-2026-42294 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-42294?
CVE-2026-42294 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42294?
Yes. A fix has been recorded for CVE-2026-42294. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42294 affect?
CVE-2026-42294 affects Argo Workflows (Kubernetes). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42294?
Upgrade to v3.7.14+ or v4.0.5+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can POST oversized payloads to /api/v1/events/, causing OOM and DoS of Argo Server.
Patch when possible
- affected< 3.7.14
- affected>= 4.0.0 and < 4.0.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.