CVE-2026-42880

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.6Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
9.6
EG Score
9.6(medium)
EPSS
39.6%
KEV
Not listed

Published

May 7, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated May 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Kubernetes Secret Extraction via ArgoCD ServerSideDiff · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-3v3m-wc6v-x4x3

Vendor Advisories for CVE-2026-42880(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-gitops-1/argocd-image-updater-rhel8:17792114122026-05-26redhat
redhatopenshift-gitops-1/gitops-rhel9-operator:17792846852026-05-26redhat
redhatopenshift-gitops-1/argocd-rhel9:17769427992026-04-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/argoproj/argo-cd/v3—3.3.9—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 64× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 220 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 09:00 UTCEG score recompute
  16. 2026-06-28 09:00 UTCVendor advisory
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 14:18 UTCEG score recompute
  19. 2026-06-27 14:18 UTCVendor advisory
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 22:05 UTCEG score recompute
  22. 2026-06-26 22:05 UTCVendor advisory
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-17 17:53 UTCEPSS rescore
  11. 2026-06-17 02:35 UTCEG score recompute
  12. 2026-06-17 02:35 UTCVendor advisory
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-15 05:49 UTCEG score recompute
  16. 2026-06-15 05:49 UTCVendor advisory
  17. 2026-06-15 01:27 UTCEG score recompute
  18. 2026-06-15 01:27 UTCVendor advisory
  19. 2026-06-14 20:57 UTCEG score recompute
  20. 2026-06-14 20:57 UTCVendor advisory
  21. 2026-06-14 16:35 UTCEG score recompute
  22. 2026-06-14 16:35 UTCVendor advisory
  23. 2026-06-14 12:13 UTCEG score recompute
  24. 2026-06-14 12:13 UTCVendor advisory
  25. 2026-06-14 07:50 UTCEG score recompute
  26. 2026-06-14 07:50 UTCVendor advisory
  27. 2026-06-14 03:29 UTCEG score recompute
  28. 2026-06-14 03:29 UTCVendor advisory
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-13 01:25 UTCEG score recompute
  31. 2026-06-13 01:25 UTCVendor advisory
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 21:01 UTCEG score recompute
  35. 2026-06-12 21:01 UTCVendor advisory
  36. 2026-06-12 10:40 UTCEG score recompute
  37. 2026-06-12 10:40 UTCVendor advisory
  38. 2026-06-12 06:19 UTCEG score recompute
  39. 2026-06-12 06:19 UTCVendor advisory
  40. 2026-06-12 01:58 UTCEG score recompute
  41. 2026-06-12 01:58 UTCVendor advisory
  42. 2026-06-11 21:36 UTCEG score recompute
  43. 2026-06-11 21:36 UTCVendor advisory
  44. 2026-06-11 17:15 UTCEG score recompute
  45. 2026-06-11 17:15 UTCVendor advisory
  46. 2026-06-11 14:00 UTCEPSS rescore
  47. 2026-06-11 11:16 UTCEG score recompute
  48. 2026-06-11 11:16 UTCVendor advisory
  49. 2026-06-11 06:45 UTCEG score recompute
  50. 2026-06-11 06:45 UTCVendor advisory
  51. 2026-06-11 02:24 UTCEG score recompute
  52. 2026-06-11 02:24 UTCVendor advisory
  53. 2026-06-10 22:18 UTCEPSS rescore
  54. 2026-06-10 21:59 UTCEG score recompute
  55. 2026-06-10 21:59 UTCVendor advisory
  56. 2026-06-10 17:38 UTCEG score recompute
  57. 2026-06-10 17:38 UTCVendor advisory
  58. 2026-06-10 13:22 UTCEPSS rescore
  59. 2026-06-10 13:22 UTCEPSS rescore
  60. 2026-06-10 13:17 UTCEG score recompute
  61. 2026-06-10 13:17 UTCVendor advisory
  62. 2026-06-10 08:56 UTCEG score recompute
  63. 2026-06-10 08:56 UTCVendor advisory
  64. 2026-06-10 04:35 UTCEG score recompute
  65. 2026-06-10 04:35 UTCVendor advisory
  66. 2026-06-10 00:12 UTCEG score recompute
  67. 2026-06-10 00:12 UTCVendor advisory
  68. 2026-06-09 19:51 UTCEG score recompute
  69. 2026-06-09 19:51 UTCVendor advisory
  70. 2026-06-09 15:29 UTCEG score recompute
  71. 2026-06-09 15:29 UTCVendor advisory
  72. 2026-06-09 11:08 UTCEG score recompute
  73. 2026-06-09 11:08 UTCVendor advisory
  74. 2026-06-09 06:47 UTCEG score recompute
  75. 2026-06-09 06:47 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42880?
CVE-2026-42880 is a critical vulnerability published on May 7, 2026. 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…
When was CVE-2026-42880 disclosed?
CVE-2026-42880 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42880 actively exploited?
CVE-2026-42880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42880?
CVE-2026-42880 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-42880?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42880, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42880

Explore →

Is Your Infrastructure Affected by CVE-2026-42880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs