NPM · AUGUST 2026 · EARLY WARNING

argocd-mcp npm Package Vulnerability: Critical CVE-2026-82456 Alert

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
CRITICAL
CVSS
10
Affected component
argocd-mcp (npm)
Affected versions
>= v0.8.0, <= v0.8.0
Patched version
Not yet available
CVE-2026-82456

An early warning has been issued for a critical vulnerability in the argocd-mcp npm package version 0.8.0. This vulnerability allows unauthorized access to Argo CD resources if ARGOCD_API_TOKEN is configured.

What happened

The argocd-mcp npm package version 0.8.0 reportedly binds its HTTP transport to every network interface and accepts MCP sessions without requiring caller credentials when ARGOCD_API_TOKEN is configured. This vulnerability, tracked as CVE-2026-82456, allows attackers who can reach the listener to invoke the full tool surface using the operator's stored token. This can lead to the creation of applications, requests for syncs, and modifications to Argo CD resources without proper authorization.

To assess your exposure, check if you are using argocd-mcp npm package version 0.8.0 and if ARGOCD_API_TOKEN is configured in your environment. If so, you may be vulnerable to this critical issue.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If argocd-mcp is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using argocd-mcp npm package version 0.8.0 and ARGOCD_API_TOKEN is configured.

What should I do right now?

Upgrade to a non-affected version of argocd-mcp and rotate the ARGOCD_API_TOKEN if it is compromised.

Is there an official fix available?

No official fix has been published yet. Monitor the primary sources for updates.

Sources

Join the 0Day waitlist →

← Back to all threats