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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2020-11009: 1.37% estimated exploitation activity in the next 30 days; percentile 72.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

29 Apr 2020, 16:31 UTC

Last modified by the source

1 Feb 2023, 05:03 UTC

Source last checked

26 Oct 2026, 16:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5679-7qrc-5m7j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11009

Advisory: IDOR can reveal execution data and logs to unauthorized user in Rundeck
IDs: CVE-2020-11009, GHSA-5679-7qrc-5m7j
Record: https://patchnext.com/advisories/cve-2020-11009 (revision 1, source checked 26 Oct 2026, 16:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.rundeck:rundeck 3.2.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.rundeck:rundeck: affected < 3.2.6; fixed in 3.2.6

## Suggested inspection (read-only)
- Maven org.rundeck:rundeck: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.rundeck:rundeck.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5679-7qrc-5m7j (GitHub-reviewed advisory GHSA-5679-7qrc-5m7j lists affected ranges: Maven org.rundeck:rundeck >=0 <3.2.6)

Commands are suggestions: review each one before running it.