Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7

Argo CD Unauthenticated Denial of Service (DoS) Vulnerability via /api/webhook Endpoint

CVE-2024-40634GHSA-jmvp-698c-4x3w

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.

Add to your agent

Affected packages

  • Go github.com/argoproj/argo-cd/v2

    Affected
    < 2.9.20>= 2.10.0, < 2.10.15>= 2.11.0, < 2.11.6
    Fixed in
    2.11.6, 2.9.20, 2.10.15

  • Go github.com/argoproj/argo-cd

    Affected
    >= 1.0.0, <= 1.8.7
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-40634: 1.39% estimated exploitation activity in the next 30 days; percentile 72.39 (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 This report details a security vulnerability in Argo CD, where an unauthenticated attacker can send a specially crafted large JSON payload to the /api/webhook endpoint, causing excessive memory allocation that leads to service disruption by triggering an Out Of Memory (OOM) kill. The issue poses a high risk to the availability of Argo CD deployments. Details The webhook server always listens to requests. By default, the endpoint doesn't require authentication. It's possible to send a large, malicious request with headers (in this case "X-GitHub-Event: push") that will make ArgoCD start allocating memory to parse the incoming request. Since the request can be constructed client-side without allocating large amounts of memory, it can be arbitrarily large. Eventually, the argocd-server component will get OOMKilled as it consumes all its available memory. The fix would be to enforce a limit on the size of the request being parsed. PoC Port-forward to the argocd-server service,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-jmvp-698c-4x3w

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-2024-40634

Advisory: Argo CD Unauthenticated Denial of Service (DoS) Vulnerability via /api/webhook Endpoint
IDs: CVE-2024-40634, GHSA-jmvp-698c-4x3w
Record: https://patchnext.com/advisories/cve-2024-40634 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.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-cd/v2 2.11.6, 2.10.15, 2.9.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected < 2.9.20; >= 2.10.0, < 2.10.15; >= 2.11.0, < 2.11.6; fixed in 2.11.6, 2.9.20, 2.10.15
- Go github.com/argoproj/argo-cd: affected >= 1.0.0, <= 1.8.7

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd: 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-cd/v2, github.com/argoproj/argo-cd.
- 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-jmvp-698c-4x3w (GitHub-reviewed advisory GHSA-jmvp-698c-4x3w lists affected ranges: Go github.com/argoproj/argo-cd >=1.0.0 =0 =2.10.0 =2.11.0 <2.11.6)

Commands are suggestions: review each one before running it.

Loading voting…