CVE-2022-29186

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: 1.2% (68th 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
9.1EG
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: 1.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Rundeck community and rundeck-enterprise docker images contained a pre-generated SSH keypair. If the id_rsa.pub public key of the keypair was copied to authorized_keys files on remote host, those hosts would allow access to anyone with the exposed private credentials. This misconfiguration only impacts Rundeck Docker instances of PagerDuty® Process Automation On Prem (formerly Rundeck) version 4.0 and earlier, not Debian, RPM or .WAR. Additionally, the id_rsa.pub file would have to be copied from the Docker image filesystem contents without overwriting it and used to configure SSH access on a host. A patch on Rundeck's main branch has removed the pre-generated SSH key pair, but it does not remove exposed keys that have been configured. To patch, users must run a script on hosts in their environment to search for exposed keys and rotate them. Two workarounds are available: Do not use any pre-existing public key file from the rundeck docker images to allow SSH access by adding it to authorized_keys files and, if you have copied the public key file included in the docker image, remove it from any authorized_keys files.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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.
Exploitation1.2% × 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
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.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
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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 (2)

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

Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise · Advisory · rundeck/rundeck · GitHub

https://github.com/rundeck/rundeck/security/advisories/GHSA-qxjx-xr2m-hgqx
GitHub commit Patch Available

commit 16ef7a70b202 (rundeck/rundeck)

Patch available: rundeck/rundeck v4.17.5 (contains commit 16ef7a70b202)

https://github.com/rundeck/rundeck/commit/16ef7a70b202492f9fbb54d8af4bb8ea0afa10ad

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 44× 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 214 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 115 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-29186?
CVE-2022-29186 is a critical-severity vulnerability; its CVE record was published on May 20, 2022. Rundeck is an open source automation service with a web console, command line tools and a WebAPI. Rundeck community and rundeck-enterprise docker images contained a pre-generated SSH keypair. If the idrsa.pub public key of the keypair was copied to authorizedkeys files on remote host, those hosts…
When was the CVE record for CVE-2022-29186 published?
The CVE record for CVE-2022-29186 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-29186 actively exploited?
CVE-2022-29186 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-2022-29186?
CVE-2022-29186 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2022-29186?
A fix for CVE-2022-29186 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-29186

Explore →

Is Your Infrastructure Affected by CVE-2022-29186?

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