CVE-2026-42880

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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, secondary
Elevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.6Exploit: Elevated riskExposed services: Not assessed

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.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

Published

May 7, 2026

Last Modified

September 7, 2026

Advisory Details (7)

Auto-updated Oct 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
githubMentions a patch (unverified)🟡 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
redhat

2467882 – (CVE-2026-42880) CVE-2026-42880 argoproj/argo-cd: Argo CD: Information disclosure of Kubernetes Secret data via Server-Side Apply dry-run mechanism

https://bugzilla.redhat.com/show_bug.cgi?id=2467882
redhatMentions a patch (unverified)

CVE-2026-42880 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-42880
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20947
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20943
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHBA-2026:12433

Patch Availability(3)

Vendor / EcosystemFix (by version range) / 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

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/argoproj/argo-cd—
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v2—
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v3—
  • 3.2.0 up to 3.2.11: fixed in 3.2.11
  • 3.3.0 up to 3.3.9: fixed in 3.3.9
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 22× 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 310 total refreshes for this CVE.

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

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 on May 7, 2026, with the most recent update on September 7, 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 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42880?
CVE-2026-42880 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42880?
A fix for CVE-2026-42880 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42880 are linked in the Vendor Advisories panel on this page.

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.