CVE-2023-40029

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2023-09-11. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2023-2497 (ENISA EUVD) · GHSA-fwr2-64vr-xv9m (GitHub Security Advisories) · GO-2023-2049 (OSV.dev)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored inkubectl.kubernetes.io/last-applied-configuration annotation. pull request #7139 introduced the ability to manage cluster labels and annotations. Since clusters are stored as secrets it also exposes the kubectl.kubernetes.io/last-applied-configuration annotation which includes full secret body. In order to view the cluster annotations via the Argo CD API, the user must have clusters, get RBAC access. Note: In many cases, cluster secrets do not contain any actually-secret information. But sometimes, as in bearer-token auth, the contents might be very sensitive. The bug has been patched in versions 2.8.3, 2.7.14, and 2.6.15. Users are advised to upgrade. Users unable to upgrade should update/deploy cluster secret with server-side-apply flag which does not use or rely on kubectl.kubernetes.io/last-applied-configuration annotation. Note: annotation for existing secrets will require manual removal.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.2%
EPSS %ILE
68th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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

September 7, 2023

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

Cluster secret might leak in cluster details page · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-fwr2-64vr-xv9m
GitHub pull request

feat: support adding labels and annotations to cluster secret (#7115)

Fix merged in argoproj/argo-cd PR #7139 on 2021-09-09 — awaiting tagged release

https://github.com/argoproj/argo-cd/pull/7139
GitHub commit

commit 4b2e5b06bff2 (argoproj/argo-cd)

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

https://github.com/argoproj/argo-cd/commit/4b2e5b06bff2ffd8ed1970654ddd8e55fc4a41c4

Vendor Advisories for CVE-2023-40029(1)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/argocd-rhel8:v1.8.5-12023-09-08redhat
redhatopenshift-gitops-1/argocd-rhel8:v1.9.2-22023-09-08redhat
gogithub.com/argoproj/argo-cd/v2 @ 2.6.15 (fixes >= 2.2.0, < 2.6.15)—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.7.14 (fixes >= 2.7.0, < 2.7.14)—ghsa
gogithub.com/argoproj/argo-cd/v2 @ 2.8.3 (fixes >= 2.8.0, < 2.8.3)—ghsa

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—
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v2—
  • 2.2.0 up to 2.6.15: fixed in 2.6.15
  • 2.7.0 up to 2.7.14: fixed in 2.7.14
  • 2.8.0 up to 2.8.3: fixed in 2.8.3
—

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 21× in last 7d / 74× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 316 rows 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 216 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-40029?
CVE-2023-40029 is a critical-severity vulnerability; its CVE record was published on September 7, 2023. Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively using Argo CD / kubectl apply. As a result, the full secret body is stored inkubectl.kubernetes.io/last-applied-configuration annotation. pull request #7139 introduced the ability…
When was the CVE record for CVE-2023-40029 published?
The CVE record for CVE-2023-40029 was published on September 7, 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-40029 actively exploited?
CVE-2023-40029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (68th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-40029?
CVE-2023-40029 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2023-40029?
A fix for CVE-2023-40029 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-40029 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-40029

Explore →

Is Your Infrastructure Affected by CVE-2023-40029?

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