CVE-2022-25175 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in org.jenkins-ci.plugins.workflow:workflow-multibranch. A fix is available for org.jenkins-ci.plugins.workflow:workflow-multibranch — see the affected versions and patch details below.
Jenkins Pipeline: Multibranch Plugin vulnerable to OS Command Injection
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-25175 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.plugins.workflow:workflow-multibranchReal-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
Jenkins Pipeline: Multibranch Plugin 706.vd43c65dec013 and earlier uses the same checkout directories for distinct SCMs for the readTrusted step, allowing attackers with Item/Configure permission to invoke arbitrary OS commands on the controller through crafted SCM contents.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins.workflow:workflow-multibranch | all versions | 707.v71c3f0a_6ccdborg.jenkins-ci.plugins.workflow:workflow-multibranch:707.v71c3f0a_6ccdb |
Affected Products
pipeline\jenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-multibranch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins.workflow:workflow-multibranch to 707.v71c3f0a_6ccdb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25175 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-2-plugins-0:3.11.1650371376-1.el7 | RHSA-2022:1420 |
| Red Hat OpenShift Container Platform 4.10 | jenkins-2-plugins-0:4.10.1647505461-1.el8 | RHSA-2022:1025 |
| Red Hat OpenShift Container Platform 4.6 | jenkins-2-plugins-0:4.6.1650364520-1.el8 | RHSA-2022:1620 |
| Red Hat OpenShift Container Platform 4.7 | jenkins-2-plugins-0:4.7.1648800585-1.el8 | RHSA-2022:1248 |
| Red Hat OpenShift Container Platform 4.8 | jenkins-2-plugins-0:4.8.1646993358-1.el8 | RHSA-2022:0871 |
| Red Hat OpenShift Container Platform 4.9 | jenkins-2-plugins-0:4.9.1647580879-1.el8 | RHSA-2022:1021 |
Frequently Asked Questions
Is CVE-2022-25175 in your dependencies?
Find it across Maven, including transitive dependencies.