Argocd-Mcp (0.8.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/argocd-mcp-0.8.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 29 Aug 2026 17:40:31 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgUnauthenticated Remote Access in argocd-mcp via CVE-2026-82456https://feed.craftedsignal.io/briefs/2026-08-argocd-mcp-unauth-access/Sat, 29 Aug 2026 17:40:31 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-argocd-mcp-unauth-access/The argocd-mcp component version 0.8.0 insecurely binds its HTTP transport to all network interfaces and lacks authentication for MCP sessions when an API token is present, allowing remote attackers to perform unauthorized Argo CD resource modifications.CVE-2026-82456 describes a critical security vulnerability in argocd-mcp version 0.8.0, an interface component for Argo CD. The software is configured to bind its HTTP transport service to all available network interfaces, including those exposed to external or untrusted networks. Furthermore, the application fails to validate the identity of callers when an ARGOCD_API_TOKEN environment variable is present, effectively trusting any request received by the listener. An attacker with network reachability to the argocd-mcp service can leverage this flaw to impersonate the legitimate operator. By submitting malicious MCP (Model Context Protocol) sessions, an unauthenticated attacker can invoke the full tool surface, resulting in the ability to create new applications, trigger unauthorized synchronization tasks, and modify sensitive Argo CD resources. This vulnerability carries a CVSS v3.1 base score of 10.0, highlighting the severe risk to CI/CD pipeline integrity and infrastructure control.

Impact

Successful exploitation allows remote, unauthenticated attackers to gain full administrative control over the Argo CD tool surface. This can lead to the deployment of malicious container images, unauthorized modification of production configurations, and complete compromise of the CD pipeline. The target scope includes any environment where argocd-mcp 0.8.0 is deployed with the ARGOCD_API_TOKEN configuration.

Recommendation

  • Immediately restrict network access to the argocd-mcp service using host-based firewalls or network policies to ensure it is only reachable from authorized local contexts.
  • Audit logs for unexpected MCP session initiations or API calls originating from unauthorized or external IP addresses.
  • Monitor for unauthorized application creation or synchronization tasks within the Argo CD instance that do not correlate with legitimate CI/CD pipeline activity.
  • Upgrade to a patched version of argocd-mcp immediately upon release by the Argo Project.
]]>criticaladvisoryvulnerabilityremote-code-executioncloud-nativecicd