Argo Workflows (Argo Server, webhook interceptor /api/v1/events/): The webhook interceptor buffers the entire request

Impact

The webhook interceptor buffers the entire request body before it authenticates or verifies the signature, so a multi-gigabyte POST to the publicly reachable /api/v1/events/ endpoint drives Argo Server into OOM. Losing Argo Server takes down the UI and API that every tenant uses to submit and inspect workflows.

Who can reach it

Any unauthenticated host that can reach the Argo Server event endpoint. That is the internet wherever the webhook path is exposed for CI or Git integrations.

What to do

Upgrade Argo Server to 3.7.14 or 4.0.5 and restart. As defense in depth, cap request body size at the ingress or service mesh in front of /api/v1/events/ and set a memory limit on the Argo Server pod so an OOM restarts one pod instead of pressuring the node.

References

Related entries

• Podman: Image env var with a key and no value causes Podman to pass the host's value of that variableCVE-2026-57231 · PodmanHigh
• Envoy: malformed upstream response trailers dispatch through a freed decoder and crash the proxyCVE-2026-73513 · Envoy (oghttp2 upstream HTTP/2 codec, ClientStreamImpl)High
• Envoy: duplicate Host headers escape request header limits and let a client OOM-kill the proxyCVE-2026-73550 · Envoy (HTTP/2 duplicate Host header handling, header-limit accounting)High
• Skipper: OPA body policies authorize oversized requests because truncated_body is derived from Content-LengthCVE-2026-86043 · Skipper HTTP router (opaAuthorizeRequestWithBody / OPA body truncation)High
• Envoy: Type-confusion in default certificate validationCVE-2022-21656 · EnvoyHigh
• Rancher: Missing authorization allows an authenticated user to create a shell pod with kubectl accessCVE-2022-21953 · RancherHigh