CVE-2023-23947

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.1EG
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.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All Argo CD versions starting with 2.3.0-rc1 and prior to 2.3.17, 2.4.23 2.5.11, and 2.6.2 are vulnerable to an improper authorization bug which allows users who have the ability to update at least one cluster secret to update any cluster secret. The attacker could use this access to escalate privileges (potentially controlling Kubernetes resources) or to break Argo CD functionality (by preventing connections to external clusters). A patch for this vulnerability has been released in Argo CD versions 2.6.2, 2.5.11, 2.4.23, and 2.3.17. Two workarounds are available. Either modify the RBAC configuration to completely revoke all clusters, update access, or use the destinations and clusterResourceWhitelist fields to apply similar restrictions as the namespaces and clusterResources fields.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-23). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

February 16, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Jul 23, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Users with any cluster secret update access may update out-of-bounds cluster secrets · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-3jfq-742w-xg8j
GitHub commit

commit fbb0b99b1ac3 (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit fbb0b99b1ac3 — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/fbb0b99b1ac3361b253052bd30259fa43a520945

Vendor Advisories for CVE-2023-23947(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/argocd-rhel8:v1.6.5-52023-02-17redhat
redhatopenshift-gitops-1/argocd-rhel8:v1.7.2-52023-02-17redhat
redhatopenshift-gitops-1/argocd-rhel8:v1.5.10-62023-02-17redhat

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

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/argoproj/argo-cd—
  • 2.3.0 up to 2.3.17: fixed in 2.3.17
  • 2.4.0 up to 2.4.23: fixed in 2.4.23
  • 2.5.0 up to 2.5.11: fixed in 2.5.11
  • 2.6.0 up to 2.6.2: fixed in 2.6.2
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v2—
  • 2.3.0 up to 2.3.17: fixed in 2.3.17
  • 2.4.0 up to 2.4.23: fixed in 2.4.23
  • 2.5.0 up to 2.5.11: fixed in 2.5.11
  • 2.6.0 up to 2.6.2: fixed in 2.6.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 55× 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 98 of 228 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2023:0802

Frequently asked(5)

What is CVE-2023-23947?
CVE-2023-23947 is a critical-severity vulnerability; its CVE record was published on February 16, 2023. Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All Argo CD versions starting with 2.3.0-rc1 and prior to 2.3.17, 2.4.23 2.5.11, and 2.6.2 are vulnerable to an improper authorization bug which allows users who have the ability to update at least one cluster secret to…
When was the CVE record for CVE-2023-23947 published?
The CVE record for CVE-2023-23947 was published on February 16, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-23947 actively exploited?
CVE-2023-23947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-23947?
CVE-2023-23947 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2023-23947?
A fix for CVE-2023-23947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-23947 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-2023-23947

Explore →

Is Your Infrastructure Affected by CVE-2023-23947?

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

Book a Demo →Browse All CVEs