How severe is GHSA-3jmw-c69h-426c?

GHSA-3jmw-c69h-426c has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3jmw-c69h-426c?

GHSA-3jmw-c69h-426c affects the following packages: org.rundeck:rundeck-core (Maven), org.rundeck:rundeck-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-3jmw-c69h-426c?

Update org.rundeck:rundeck-core to 3.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jmw-c69h-426c is resolved across your whole dependency graph.

How do I detect GHSA-3jmw-c69h-426c in my Maven dependencies?

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

How do I mitigate GHSA-3jmw-c69h-426c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-3jmw-c69h-426c actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jmw-c69h-426c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3jmw-c69h-426c?

GHSA-3jmw-c69h-426c has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3jmw-c69h-426c?

GHSA-3jmw-c69h-426c is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3jmw-c69h-426c published, and has it been updated?

GHSA-3jmw-c69h-426c was published on September 1, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Cross-Site Request Forgery (CSRF) can run untrusted code on Rundeck serverGHSA-3jmw-c69h-426c

HIGHFix: rundeck/rundeck@67c4eed

GHSA-3jmw-c69h-426c is a high-severity (CVSS 7.2) Cross-Site Request Forgery (CSRF) vulnerability in org.rundeck:rundeck-core. A fix is available for org.rundeck:rundeck-core — see the affected versions and patch details below.

Also known asCVE-2021-39133

Published

Sep 1, 2021

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-3jmw-c69h-426c by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.rundeck:rundeck-core☕org.rundeck:rundeck-core

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

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 [email protected]

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.rundeck:rundeck-core`	≥ 3.4.0&&< 3.4.3	3.4.3`org.rundeck:rundeck-core:3.4.3`
☕Maven	`org.rundeck:rundeck-core`	all versions	3.3.14`org.rundeck:rundeck-core:3.3.14`

Affected Products

1 product · 2 configurations

Application

rundeckpagerduty

≥ 3.4.0 && < 3.4.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.rundeck:rundeck-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.rundeck:rundeck-core to 3.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jmw-c69h-426c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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](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 [[email protected]](mailto:[email protected]) To report security issues to Rundeck please use the form at [https://rund