CVE-2026-108585
Deferred Deferred - Pending Action

Path Traversal in Argo CD MCP Server

Publication date: 2026-10-10

Last updated on: 2026-10-10

Assigner: VulnCheck

Description
argocd-mcp (Argo CD MCP Server) through 0.9.0 contains a path traversal vulnerability in the delete_application tool that allows MCP clients to reach unintended API endpoints via unvalidated applicationName values. Attackers or prompt-injected models can supply dot-segment values like ../repositories/ to send authenticated DELETE requests deleting repositories, clusters, or projects within the token's RBAC permissions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-10
Last Modified
2026-10-10
Generated
2026-10-10
AI Q&A
2026-10-10
EPSS Evaluated
N/A
NVD
CVE-2026-108585
EUVD
EUVD-2026-96372

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
argoproj-labs argocd-mcp 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a path traversal flaw in the argocd-mcp server (version 0.9.0 or earlier). It allows attackers to manipulate the applicationName parameter in the delete_application tool to bypass intended API endpoints. By using dot-segment values like ../repositories/, the attacker can redirect DELETE requests to unintended targets such as repositories, clusters, or projects within the token's RBAC permissions.

Detection Guidance

Check for unauthorized DELETE requests to ArgoCD API endpoints by monitoring logs for paths containing ../repositories/, ../clusters/, or ../projects/. Use tools like curl to test if the delete_application tool accepts malicious applicationName values with path traversal sequences.

Impact Analysis

An attacker could exploit this to delete critical resources like repositories, clusters, or projects within the ArgoCD server if they have sufficient permissions. This could disrupt operations, cause data loss, or lead to unauthorized modifications depending on the RBAC permissions of the compromised token.

Compliance Impact

This vulnerability could lead to unauthorized data deletion or modification, violating integrity and availability requirements in GDPR and HIPAA. It may result in non-compliance due to unauthorized access to sensitive data or systems, potentially triggering reporting obligations and fines under these regulations.

Mitigation Strategies

Upgrade argocd-mcp to a patched version beyond 0.9.0. Validate applicationName inputs in delete_application to reject dot-segments and enforce single path segments. Restrict RBAC permissions for ArgoCD tokens to prevent unauthorized deletions.

Chat Assistant

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

EPSS Chart