Rundeck vulnerabilitiesRanked by how likely they are to be used.

Product46 versions
The short answer

Rundeck is made by Jenkins. We track 7 published vulnerabilities in it, across 46 versions. None of them is on the list of flaws known to be exploited today. If you run Rundeck, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Rundeck vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Rundeck's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Rundeck flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 73%

    Jenkins Rundeck Plugin 3.6.10 and earlier does not restrict URL schemes in Rundeck webhook submissions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to submit crafted...

    CVSS5.4Published17 May 2022
  2. 1.1%

    Jenkins Rundeck Plugin 3.6.6 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

    CVSS7.1Published9 Mar 2020
  3. 1.0%

    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.

    CVSS8.8Published21 Sep 2022
  4. 0.9%

    Jenkins Rundeck Plugin 3.6.5 and earlier stores credentials unencrypted in its global configuration file and in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read...

    CVSS6.5Published17 Dec 2019
  5. 0.7%

    A cross-site request forgery vulnerability in Jenkins Rundeck Plugin allows attackers to connect to an attacker-specified URL using attacker-specified credentials.

    CVSS4.3Published16 Oct 2019
  6. 0.6%

    A missing permission check in Jenkins Rundeck Plugin allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials.

    CVSS4.3Published16 Oct 2019
  7. 0.6%

    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...

    CVSS4.3Published21 Sep 2022
Precursor Intelligence

Running Rundeck? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 7 published vulnerabilities listed under the name Rundeck, across 46 versions.

None of Rundeck's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Rundeck. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.