CVE-2026-82456
Auth bypass in argocd-mcp 0.8.0 allows remote use of stored Argo CD operator token
Is CVE-2026-82456 being exploited?
Not confirmed. CVE-2026-82456 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-82456?
CVE-2026-82456 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82456?
Yes. A fix has been recorded for CVE-2026-82456. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82456 affect?
CVE-2026-82456 affects argocd-mcp 0.8.0, Argo CD instances using ARGOCD_API_TOKEN, Kubernetes clusters running argocd-mcp. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82456?
Upgrade argocd-mcp to patched release, restrict listener to trusted interfaces, rotate ARGOCD_API_TOKEN
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote full Argo CD control: create/modify applications, trigger syncs, and alter Argo CD resources using operator token
Immediate action required
- affected>= 0.8.0 and < 0.9.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.