CVE-2022-29165

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 2.1% (81st 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
10.0EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.1%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A critical vulnerability has been discovered in Argo CD starting with version 1.4.0 and prior to versions 2.1.15, 2.2.9, and 2.3.4 which would allow unauthenticated users to impersonate as any Argo CD user or role, including the admin user, by sending a specifically crafted JSON Web Token (JWT) along with the request. In order for this vulnerability to be exploited, anonymous access to the Argo CD instance must have been enabled. In a default Argo CD installation, anonymous access is disabled. The vulnerability can be exploited to impersonate as any user or role, including the built-in admin account regardless of whether it is enabled or disabled. Also, the attacker does not need an account on the Argo CD instance in order to exploit this. If anonymous access to the instance is enabled, an attacker can escalate their privileges, effectively allowing them to gain the same privileges on the cluster as the Argo CD instance, which is cluster admin in a default installation. This will allow the attacker to create, manipulate and delete any resource on the cluster. They may also exfiltrate data by deploying malicious workloads with elevated privileges, thus bypassing any redaction of sensitive data otherwise enforced by the Argo CD API. A patch for this vulnerability has been released in Argo CD versions 2.3.4, 2.2.9, and 2.1.15. As a workaround, one may disable anonymous access, but upgrading to a patched version is preferable.

CVSS v3
10.0
EG Score
10.0CRITICALmedium 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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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
2.1%
EPSS %ILE
81st
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 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
2.1% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

May 20, 2022

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Oct 17, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Argo CD will trust invalid JWT claims if anonymous access is enabled · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-r642-gv9p-2wjj
GitHub release Patch Available

v2.3.4

Patch available: argoproj/argo-cd v2.3.4

https://github.com/argoproj/argo-cd/releases/tag/v2.3.4
GitHub release Patch Available

v2.2.9

Patch available: argoproj/argo-cd v2.2.9

https://github.com/argoproj/argo-cd/releases/tag/v2.2.9
GitHub release Patch Available

v2.1.15

Patch available: argoproj/argo-cd v2.1.15

https://github.com/argoproj/argo-cd/releases/tag/v2.1.15

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-gitops-1/kam-delivery-rhel8:v1.3.9-32022-05-18redhat
redhatopenshift-gitops-1/kam-delivery-rhel8:v1.5.1-42022-05-18redhat
redhatopenshift-gitops-1/kam-delivery-rhel8:v1.3.10-12022-05-18redhat
redhatopenshift-gitops-1/kam-delivery-rhel8:v1.4.7-22022-05-18redhat

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 up to 2.1.15: fixed in 2.1.15
  • every version on: no fix on record
—
github.com/argoproj/argo-cd/v2—
  • 2.3.0 up to 2.3.4: fixed in 2.3.4
  • 2.2.0 up to 2.2.9: fixed in 2.2.9
  • every version up to 2.1.15: fixed in 2.1.15
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 57× 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 99 of 222 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-29165?
CVE-2022-29165 is a critical-severity vulnerability; its CVE record was published on May 20, 2022. Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. A critical vulnerability has been discovered in Argo CD starting with version 1.4.0 and prior to versions 2.1.15, 2.2.9, and 2.3.4 which would allow unauthenticated users to impersonate as any Argo CD user or role, including…
When was the CVE record for CVE-2022-29165 published?
The CVE record for CVE-2022-29165 was published on May 20, 2022. 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-2022-29165 actively exploited?
CVE-2022-29165 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% probability of exploitation in the next 30 days (81st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-29165?
CVE-2022-29165 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2022-29165?
A fix for CVE-2022-29165 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-29165 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-2022-29165

Explore →

Is Your Infrastructure Affected by CVE-2022-29165?

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