Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server

Exploitation

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

CVSS

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

EPSS

• CVE-2021-39133: 0.45% estimated exploitation activity in the next 30 days; percentile 39.39 (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 A user with admin access to the system resource type is potentially vulnerable to a CSRF attack that could cause the server to run untrusted code on all Rundeck editions. Patches Available in Rundeck 3.4.3 and 3.3.14 Workarounds Please visit https://rundeck.com/security for information about specific workarounds. For more information If you have any questions or comments about this advisory: Email us at security@rundeck.com To report security issues to Rundeck please use the form at https://rundeck.com/security

Published by the source

1 Sep 2021, 18:26 UTC

Last modified by the source

1 Feb 2023, 05:06 UTC

Source last checked

26 Oct 2026, 16:07 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3jmw-c69h-426c

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

# Patch Next advisory brief: CVE-2021-39133

Advisory: Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck server
IDs: CVE-2021-39133, GHSA-3jmw-c69h-426c
Record: https://patchnext.com/advisories/cve-2021-39133 (revision 1, source checked 26 Oct 2026, 16:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
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-core 3.4.3, 3.3.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.rundeck:rundeck-core: affected >= 3.4.0, < 3.4.3; < 3.3.14; fixed in 3.3.14, 3.4.3

## Suggested inspection (read-only)
- Maven org.rundeck:rundeck-core: 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-core.
- 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-3jmw-c69h-426c (GitHub-reviewed advisory GHSA-3jmw-c69h-426c lists affected ranges: Maven org.rundeck:rundeck-core >=3.4.0 =0 <3.3.14)

Commands are suggestions: review each one before running it.