Skip to main content
VulnerabilityPublished Updated

CVE-2024-22424: argoproj argo-cd · Cross-Site Request Forgery (CSRF)

Affects argoproj argo-cdSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High · fixed in 2.10-rc2 : patch argoproj argo-cd soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.10-rc2, 2.9.4, 2.8.8 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade argoproj/argo-cd to 2.10-rc2, 2.9.4, 2.8.8 or 2.7.15.

Affected software

ProductAffectedFixed in
GitHubargoproj/argo-cdpkg:github/argoproj/argo-cdOther threatsAffected
  • <2.7.15
  • >=2.7.0 <2.7.15
  • <2.8.8
  • <2.9.4
  • <2.10-rc2
Fixed in
  • 2.7.15
  • 2.8.8
  • 2.9.4
  • 2.10-rc2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate upgrade to Argo CD versions 2.10-rc2, 2.9.4, 2.8.8, or 2.7.15 or later to apply the patch that enforces strict Content-Type validation on API requests.
  2. Audit internal web applications and portals hosted on sibling or parent domains to ensure they cannot be used to inject malicious HTML or scripts that could trigger CSRF attacks.
  3. Implement strict Content Security Policy (CSP) headers on internal web applications to reduce the risk of malicious script injection.
  4. Restrict access to Argo CD API endpoints to trusted networks and users, minimizing exposure.
  5. Monitor Argo CD API logs for unusual or unauthorized API calls that could indicate exploitation attempts.
  6. Educate users about phishing risks and the dangers of clicking on untrusted links, especially within internal domains.
  7. Consider network segmentation to isolate Argo CD instances and related internal web services to reduce the attack surface.
  8. Review and tighten cookie policies and domain configurations to prevent cookie sharing across subdomains where possible.
  9. Regularly review and update Kubernetes and GitOps security best practices to detect and prevent supply chain attacks.

Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. The Argo CD API prior to versions 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15 are vulnerable to a cross-server request forgery (CSRF) attack when the attacker has the ability to write HTML to a page on the same parent domain as Argo CD. A CSRF attack works by tricking an authenticated Argo CD user into loading a web page which contains code to call Argo CD API endpoints on the victim’s behalf. For example, an attacker could send an Argo CD user a link to a page which looks harmless but in the background calls an Argo CD API endpoint to create an application running malicious code. Argo CD uses the “Lax” SameSite cookie policy to prevent CSRF attacks where the attacker controls an external domain. The malicious external website can attempt to call the Argo CD API, but the web browser will refuse to send the Argo CD auth token with the request. Many companies host Argo CD on an internal subdomain. If an attacker can place malicious code on, for example, https://test.internal.example.com/, they can still perform a CSRF attack. In this case, the “Lax” SameSite cookie does not prevent the browser from sending the auth cookie, because the destination is a parent domain of the Argo CD API. Browsers generally block such attacks by applying CORS policies to sensitive requests with sensitive content types. Specifically, browsers will send a “preflight request” for POSTs with content type “application/json” asking the destination API “are you allowed to accept requests from my domain?” If the destination API does not answer “yes,” the browser will block the request. Before the patched versions, Argo CD did not validate that requests contained the correct content type header. So an attacker could bypass the browser’s CORS check by setting the content type to something which is considered “not sensitive” such as “text/plain.” The browser wouldn’t send the preflight request, and Argo CD would happily accept the contents (which are actually still JSON) and perform the requested action (such as running malicious code). A patch for this vulnerability has been released in the following Argo CD versions: 2.10-rc2, 2.9.4, 2.8.8, and 2.7.15. The patch contains a breaking API change. The Argo CD API will no longer accept non-GET requests which do not specify application/json as their Content-Type. The accepted content types list is configurable, and it is possible (but discouraged) to disable the content type check completely. Users are advised to upgrade. There are no known workarounds for this vulnerability.

References

Community reviews

Loading reviews…