CVE-2026-42880
Argoproj Argo Cd information disclosure
- Published7 May 2026
Description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From versions 3.2.0 to before 3.2.11 and 3.3.0 to before 3.3.9, there is a missing authorization and data-masking gap in Argo CD's ServerSideDiff endpoint that allows an attacker with read-only access to extract plaintext Kubernetes Secret data from etcd via the Kubernetes API server's Server-Side Apply dry-run mechanism. This issue has been patched in versions 3.2.11 and 3.3.9.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NAffected products
Remediation
References
- https://access.redhat.com/errata/RHBA-2026:12433
- https://access.redhat.com/errata/RHSA-2026:20943
- https://access.redhat.com/errata/RHSA-2026:20947
- https://access.redhat.com/security/cve/CVE-2026-42880
- https://bugzilla.redhat.com/show_bug.cgi?id=2467882
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-3v3m-wc6v-x4x3
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42880.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-42880 being actively exploited?
CVE-2026-42880 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.56%.
How severe is CVE-2026-42880?
CVE-2026-42880 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.56% probability of exploitation.
Which products are affected by CVE-2026-42880?
Affected products include Argoproj Argo Cd.
How do I fix CVE-2026-42880?
Upgrade affected software to a fixed version, for example Argoproj Argo Cd 3.2.11 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-42880 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.