Vulnary
← back to the feed
Critical· 9.6official fix available

CVE-2026-42880

Argo CD versions 3.2.0 through 3.2.10 and 3.3.0 through 3.3.8 have a flaw that lets an attacker with only read‑only access read plain‑text Kubernetes secrets. The bug is in the ServerSideDiff endpoint and can be exploited via the Kubernetes API server’s dry‑run feature. The issue has been fixed in later releases.

publishedMay 7, 2026
last modifiedAug 3, 2026
sourcesNVD
severity · cvss
9.6
critical · how bad it is
exploitation · epss
<1%
40th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 19, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

argoproj argo_cd, versions 3.2.0–3.2.10 and 3.3.0–3.3.8.

02

Real-world impact

An attacker who can read from the Argo CD API can retrieve sensitive Kubernetes secret data stored in etcd, potentially exposing credentials, tokens, or other confidential information.

03

Why this severity

The CVSS score of 9.6 reflects that the vulnerability is exploitable over the network, requires only low attack complexity and low privileges, and does not need user interaction. It grants high confidentiality impact by exposing secret data, while integrity and availability are not affected.

04

What to do about it

official fix available
recommended steps
  1. 011. Check the current Argo CD version you are running.
  2. 022. Upgrade Argo CD to version 3.2.11 or later, or to 3.3.9 or later.
  3. 033. Restart the Argo CD service to apply the update.

NVD-referenced vendor advisory

05

Timeline

  1. May 7, 2026 · May 7, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 20, 2026 · 15d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  3. Aug 3, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredLow
User interactionNone needed
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
CVE-2026-42880: Argo CD versions 3.2.0 through 3.2.10 and 3.3.0 through 3.3.8 have a f · Vulnary