CVE-2026-82456
Received Received - Intake

Argocd-mcp 0.8.0 Unauthenticated Remote Code Execution

Vulnerability report for CVE-2026-82456, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-29

Last updated on: 2026-08-29

Assigner: VulnCheck

Description

argocd-mcp 0.8.0 binds its HTTP transport to every network interface and accepts MCP sessions without requiring caller credentials when ARGOCD_API_TOKEN is configured. Attackers who can reach the listener can invoke the full tool surface using the operator's stored token to create applications, request syncs, and modify Argo CD resources.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-29
Last Modified
2026-08-29
Generated
2026-08-29
AI Q&A
2026-08-29
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
argoproj argocd 0.8.0
argoproj argocd-mcp 0.8.0
argoproj argocd-mcp to 0.9.0 (exc)
argoproj argocd-mcp 0.9.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1327 The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-82456 is a critical authentication bypass in argocd-mcp 0.8.0 where the HTTP server binds to all network interfaces and accepts unauthenticated MCP sessions when ARGOCD_API_TOKEN is set. Attackers on the same network can exploit this to use the operator's stored token to create applications, request syncs, and modify Argo CD resources without credentials.

Detection Guidance

Check if argocd-mcp 0.8.0 is running and listening on all network interfaces (0.0.0.0) by using commands like 'netstat -tulnp | grep argocd-mcp' or 'ss -tulnp | grep argocd-mcp'. Verify if the service accepts unauthenticated connections by attempting to access it from a different host on the network.

Inspect the version of argocd-mcp installed using 'mcp-for-argocd --version' or by checking package managers like 'pip show argocd-mcp'. If version 0.8.0 or below is detected, the system is likely vulnerable.

Impact Analysis

An attacker could deploy unauthorized Kubernetes manifests, modify or delete applications, or exfiltrate sensitive data using the compromised Argo CD token. This could lead to full system compromise, data breaches, or service disruption if the attacker gains control over deployed resources.

Compliance Impact

This vulnerability could lead to unauthorized access and data breaches, violating GDPR's data protection requirements and HIPAA's security rules. Organizations may face fines, legal penalties, and reputational damage due to non-compliance resulting from unauthorized resource modifications or data exposure.

Mitigation Strategies

Upgrade argocd-mcp to version 0.9.0 or later immediately, as this version restricts the listener to localhost and adds authentication requirements.

If upgrading is not immediately possible, restrict the HTTP transport binding to localhost by modifying the service configuration or using firewall rules to block external access to the vulnerable port.

Disable or remove the ARGOCD_API_TOKEN environment variable if it is not required for operation, as this reduces the attack surface.

Monitor network traffic for unauthorized access attempts or unusual MCP session creation, especially from external hosts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82456. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart