How severe is GHSA-r6mc-mrvr-23cr?

GHSA-r6mc-mrvr-23cr has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-r6mc-mrvr-23cr?

GHSA-r6mc-mrvr-23cr affects the following packages: org.jenkins-ci.plugins.workflow:workflow-cps (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r6mc-mrvr-23cr?

Update org.jenkins-ci.plugins.workflow:workflow-cps to 2.64 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6mc-mrvr-23cr is resolved across your whole dependency graph.

How do I detect GHSA-r6mc-mrvr-23cr in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-cps. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r6mc-mrvr-23cr 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.

How does O3 Security protect against GHSA-r6mc-mrvr-23cr?

O3 pinpoints whether GHSA-r6mc-mrvr-23cr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r6mc-mrvr-23cr actively exploited in the wild?

Yes. There are 5 known exploit references for GHSA-r6mc-mrvr-23cr, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-r6mc-mrvr-23cr?

GHSA-r6mc-mrvr-23cr has an EPSS (Exploit Prediction Scoring System) score of 75.6%, placing it in the 99th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-r6mc-mrvr-23cr in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-r6mc-mrvr-23cr (Jenkins Matrix Project Plugin Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-15. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-r6mc-mrvr-23cr?

GHSA-r6mc-mrvr-23cr is classified as CWE-693 (CWE-693). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r6mc-mrvr-23cr published, and has it been updated?

GHSA-r6mc-mrvr-23cr was published on May 13, 2022 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-03-25 — agencies required to remediate by 2022-04-15

☕ Maven

GHSA-r6mc-mrvr-23cr

CRITICAL

Sandbox bypass in Jenkins Pipeline: Groovy Plugin

Also known asCVE-2019-1003030

Published

May 13, 2022

Updated

Oct 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

75.6%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.jenkins-ci.plugins.workflow:workflow-cps

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

A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able to control pipeline scripts to execute arbitrary code on the Jenkins master JVM.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins.workflow:workflow-cps`	all versions	2.64

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-48904webappsjava

Jenkins 2.63 - Sandbox bypass in pipeline: Groovy plug-in

by Daniel Morris · Oct 19, 2020

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-cps. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins.workflow:workflow-cps to 2.64 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6mc-mrvr-23cr 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.
How O3 protects you
O3 pinpoints whether GHSA-r6mc-mrvr-23cr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r6mc-mrvr-23cr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-r6mc-mrvr-23cr in your dependencies?

O3 detects GHSA-r6mc-mrvr-23cr across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works