CVE-2022-41234: Jenkins Rundeck Plugin · Vulnerability
Affects Jenkins Rundeck PluginSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins project Jenkins Rundeck Plugin | Affected
| Fixed in– |
AI-suggested
European organizations should take immediate and specific actions beyond generic patching advice: 1) Restrict access to the Jenkins Rundeck Plugin webhook endpoint (/plugin/rundeck/webhook/) by implementing network-level controls such as IP whitelisting or VPN-only access to Jenkins servers. 2) Review and tighten Jenkins user permissions, ensuring that Overall/Read permissions are granted only to trusted users and service accounts. 3) Implement multi-factor authentication (MFA) for all Jenkins users to reduce the risk of credential compromise. 4) Monitor Jenkins logs for unusual job trigger activity, especially from users with limited privileges, and set up alerts for anomalous webhook requests. 5) If possible, upgrade the Jenkins Rundeck Plugin to a version that addresses this vulnerability once available, or apply vendor-provided patches promptly. 6) Employ runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block unauthorized webhook invocations. 7) Conduct internal audits of Jenkins job configurations to identify and restrict jobs that are unnecessarily triggerable via Rundeck webhooks. 8) Educate development and operations teams about the risks of excessive permissions and the importance of secure plugin configurations.
Description
Jenkins Rundeck Plugin 3.6.11 and earlier does not protect access to the /plugin/rundeck/webhook/ endpoint, allowing users with Overall/Read permission to trigger jobs that are configured to be triggerable via Rundeck.