CVE-2026-15416

HIGHPre-NVD 8.98.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was identified in Argo CD, the GitOps engine used by Red Hat OpenShift GitOps, that could allow an unauthenticated attacker with network access to the Argo CD repo-server to achieve remote code execution. Under certain conditions, the attacker may then manipulate cached data to deploy malicious Kubernetes resources to managed clusters, potentially resulting in complete cluster compromise.

CVSS v3
8.9
EG Score
8.9HIGHmedium confidence
EG Risk
40
EG Risk 40/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 (value × EchelonGraph’s weight)
Severity89% × 45%
The EG Score, 8.9 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

August 11, 2026

Advisory Details (6)

Auto-updated Jul 14, 2026
Patch available. Sources: github_commit, github, redhat.
Web page

Caught in the Octopus Trap: Unauthenticated RCE in Argo CD with CodeQL

https://www.synacktiv.com/en/publications/caught-in-the-octopus-trap-unauthenticated-rce-in-argo-cd-with-codeql
Web page

Unpatched Argo CD Repo-Server Flaw Could Let Attackers Take Over Kubernetes Clusters

https://thehackernews.com/2026/07/unpatched-argo-cd-repo-server-flaw.html
GitHub advisoryMentions a patch (unverified)

Argo CD: Network policies securing repo-server are not installed by default leading to RCE · Advisory · argoproj/argo-helm · GitHub

https://github.com/argoproj/argo-helm/security/advisories/GHSA-47m3-95c7-g2g8
GitHub commit Patch Available

commit 0f245ab (argoproj/argo-helm)

Patch available: argoproj/argo-helm argo-cd-10.0.0 (contains commit 0f245ab)

https://github.com/argoproj/argo-helm/commit/0f245ab
Red Hat

2496732 – (CVE-2026-15416) CVE-2026-15416 argo-cd: Argo CD unauthenticated remote code execution in repo-server via GenerateManifest gRPC endpoint

https://bugzilla.redhat.com/show_bug.cgi?id=2496732
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-15416

Vendor Advisories for CVE-2026-15416(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/gitops-rhel8-operator:17851713392026-08-10redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 175 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-15416?
CVE-2026-15416 is a high-severity vulnerability; its CVE record was published on July 14, 2026. A flaw was identified in Argo CD, the GitOps engine used by Red Hat OpenShift GitOps, that could allow an unauthenticated attacker with network access to the Argo CD repo-server to achieve remote code execution. Under certain conditions, the attacker may then manipulate cached data to deploy…
When was CVE-2026-15416 made public?
CVE-2026-15416 was made public on July 1, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of August 11, 2026; the record at its source may have been updated since.
Is CVE-2026-15416 actively exploited?
CVE-2026-15416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15416?
CVE-2026-15416 has a CVSS base score of 8.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15416?
A fix for CVE-2026-15416 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15416 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15416

Explore →

Is Your Infrastructure Affected by CVE-2026-15416?

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

Book a Demo →Browse All CVEs