Argo Workflows: Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.2epss 0.6%
exploitation probability
0.6%top 54% of all CVEs
observed exploitation
nono source reports it
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to versions 3.7.14 and 4.0.5, the Webhook Interceptor loads the entire request body into memory before authenticating the request or verifying its signature. This occurs on the /api/v1/events/ endpoint, which is publicly accessible (albeit intended for webhooks). An attacker can send a request with an extremely large body (e.g., multiple gigabytes), causing the Argo Server to allocate excessive memory, potentially leading to an Out-Of-Memory (OOM) crash and denial of service. This issue has been patched in versions 3.7.14 and 4.0.5.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Affected products
argoproj · argo-workflowsReferences
https://access.redhat.com/security/cve/CVE-2026-42294https://bugzilla.redhat.com/show_bug.cgi?id=2468443https://github.com/argoproj/argo-workflows/commit/7abb4de6c3599e2d5d960ba4d5de4cf1df109965https://github.com/argoproj/argo-workflows/releases/tag/v3.7.14https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5https://github.com/argoproj/argo-workflows/security/advisories/GHSA-jcc8-g2q4-9fxqhttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42294.json