NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2020-11009 — rundeck

MEDIUM

CVE-2020-11009 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.rundeck:rundeck. A fix is available for org.rundeck:rundeck — see the affected versions and patch details below.

IDOR can reveal execution data and logs to unauthorized user in Rundeck

Also known asGHSA-5679-7qrc-5m7j
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.62%1.25%1.87%0.5%1.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.rundeck:rundeck

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Authenticated users can craft a request that reveals Execution data and logs and Job details that they are not authorized to see.

Depending on the configuration and the way that Rundeck is used, this could result in anything between a high severity risk, or a very low risk. If access is tightly restricted and all users on the system have access to all projects, this is not really much of an issue. If access is wider and allows login for users that do not have access to any projects, or project access is restricted, there is a larger issue. If access is meant to be restricted and secrets, sensitive data, or intellectual property are exposed in Rundeck execution output and job data, the risk becomes much higher.

Details

An authenticated user could craft a request to:

  • View Executions and download execution logs without access to read or view the associated Job, or ad-hoc resource.
  • Get the list of running executions in a project, without Event read access, if they have read access to view the project.
  • View the Options definitions of a Job without access to view the Job.
  • View the definition of a workflow step of a Job without access to view the Job.
  • View the SCM diff of a modified Job definition if SCM is enabled, without Project export access level.
  • View the New User Profile Form for a different username, without User admin access. Note: they would not be allowed to create or modify a profile for a different user, or reveal any user profile information for a different user.

Some authenticated API requests were not correctly checking appropriate authorization levels:

  • The list of running Executions would be sent without read access to Events.
  • The Plugin Input Parameters for a SCM plugin would be sent without authorization for project import,scm_import,export, or scm_export actions.
  • Job Retry action could retry an execution without read or view access to the Execution, which would reveal the Execution's option values. (run access to the Job was still required).

Patches

Upgrade to Rundeck version 3.2.6

Workarounds

None

References

3.2.6 Release Notes

Report

If you have any questions or comments about this advisory:

To report security issues to Rundeck please use the form at http://rundeck.com/security

Reporter: Justine Osborne of Apple Information Security

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.rundeck:rundeckall versions3.2.6org.rundeck:rundeck:3.2.6

Affected Products

1 product · 1 configurations
Application
rundeckpagerduty
< 3.2.6
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.rundeck:rundeck, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.rundeck:rundeck to 3.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11009 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact Authenticated users can craft a request that reveals Execution data and logs and Job details that they are not authorized to see. > Depending on the configuration and the way that Rundeck is used, this could result in anything between a high severity risk, or a very low risk. If access is tightly restricted and all users on the system have access to all projects, this is not really much of an issue. If access is wider and allows login for users that do not have access to any projects, or project access is restricted, there is a larger issue. If access is meant to be restricted an
O3 Security · Impact-Aware SCA

Is CVE-2020-11009 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-11009: rundeck — Fixed in 3.2.6