Skip to main content
VulnerabilityPublished Updated

CVE-2022-41233: Jenkins Rundeck Plugin · Missing Authorization

Affects Jenkins Rundeck PluginSource CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium : upgrade to 3.6.12 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Jenkins Rundeck Plugin to 3.6.12.

Affected software

ProductAffectedFixed in
Jenkins project Jenkins Rundeck PluginAffected
  • <3.6.12
Fixed in
  • 3.6.12

AI-suggested

To mitigate this vulnerability, European organizations should first verify the version of the Jenkins Rundeck Plugin in use and upgrade to a version where this issue is resolved once available. In the absence of an immediate patch, organizations should restrict Item/Read permissions to trusted users only, minimizing the number of accounts that can exploit this flaw. Additionally, review and tighten access control policies around Jenkins jobs and artifacts, ensuring that the optional Run/Artifacts permission is enabled only when strictly necessary and assigned carefully. Implement network segmentation and monitoring to detect unusual access patterns to Jenkins endpoints. Employ audit logging to track access to build artifacts and investigate any suspicious activity promptly. Consider isolating sensitive build artifact storage from Jenkins or using artifact repositories with stricter access controls. Finally, educate DevOps teams about the risks of excessive permissions and the importance of least privilege principles in CI/CD environments.

Description

Jenkins Rundeck Plugin 3.6.11 and earlier does not perform Run/Artifacts permission checks in multiple HTTP endpoints, allowing attackers with Item/Read permission to obtain information about build artifacts of a given job, if the optional Run/Artifacts permission is enabled.

References

Community reviews

Loading reviews…