What is CVE-2022-25179?

CVE-2022-25179 is a medium-severity security vulnerability in org.jenkins-ci.plugins.workflow:workflow-multibranch (maven), affecting versions >= 2.24, < 2.26.1. It is fixed in 2.26.1, 2.23.1, 696.698.v9b4218eea50f, 707.v71c3f0a.

How severe is CVE-2022-25179?

CVE-2022-25179 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.plugins.workflow:workflow-multibranch are affected by CVE-2022-25179?

org.jenkins-ci.plugins.workflow:workflow-multibranch (maven) versions >= 2.24, < 2.26.1 is affected.

Is CVE-2022-25179 exploitable, and should I be worried?

Whether CVE-2022-25179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-25179 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-25179

Q: How severe is CVE-2022-25179?

CVE-2022-25179 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2022-25179?

Yes. CVE-2022-25179 is fixed in 2.26.1, 2.23.1, 696.698.v9b4218eea50f, 707.v71c3f0a. Upgrade to this version or later.

Q: Is CVE-2022-25179 exploitable, and should I be worried?

Whether CVE-2022-25179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-25179 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-25179?

Upgrade: org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.26.1 or later, org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.23.1 or later, org.jenkins-ci.plugins.workflow:workflow-multibranch to 696.698.v9b4218eea50f or later, org.jenkins-ci.plugins.workflow:workflow-multibranch to 707.v71c3f0a or later.

Summary

Link Following in Jenkins Pipeline Multibranch Plugin

Jenkins Pipeline: Multibranch Plugin prior to 2.23.1, 2.26.1, 696.698.v9b4218eea50f, and 707.v71c3f0a_6ccdb_ follows symbolic links to locations outside of the checkout directory for the configured SCM when reading files using the readTrusted step, allowing attackers able to configure Pipelines permission to read arbitrary files on the Jenkins controller file system.

Impact

CVE-2022-25179 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.26.1, 2.23.1, 696.698.v9b4218eea50f, 707.v71c3f0a); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins.workflow:workflow-multibranch (>= 2.24, < 2.26.1) org.jenkins-ci.plugins.workflow:workflow-multibranch (< 2.23.1) org.jenkins-ci.plugins.workflow:workflow-multibranch (>= 696.v52535c46f4c9, < 696.698.v9b4218eea50f) org.jenkins-ci.plugins.workflow:workflow-multibranch (>= 706.vd43c65dec013, < 707.v71c3f0a)

Security releases

org.jenkins-ci.plugins.workflow:workflow-multibranch → 2.26.1 (maven) org.jenkins-ci.plugins.workflow:workflow-multibranch → 2.23.1 (maven) org.jenkins-ci.plugins.workflow:workflow-multibranch → 696.698.v9b4218eea50f (maven) org.jenkins-ci.plugins.workflow:workflow-multibranch → 707.v71c3f0a (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.26.1 or later; org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.23.1 or later; org.jenkins-ci.plugins.workflow:workflow-multibranch to 696.698.v9b4218eea50f or later; org.jenkins-ci.plugins.workflow:workflow-multibranch to 707.v71c3f0a or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-25179? CVE-2022-25179 is a medium-severity security vulnerability in org.jenkins-ci.plugins.workflow:workflow-multibranch (maven), affecting versions >= 2.24, < 2.26.1. It is fixed in 2.26.1, 2.23.1, 696.698.v9b4218eea50f, 707.v71c3f0a.
How severe is CVE-2022-25179? CVE-2022-25179 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.jenkins-ci.plugins.workflow:workflow-multibranch are affected by CVE-2022-25179? org.jenkins-ci.plugins.workflow:workflow-multibranch (maven) versions >= 2.24, < 2.26.1 is affected.
Is there a fix for CVE-2022-25179? Yes. CVE-2022-25179 is fixed in 2.26.1, 2.23.1, 696.698.v9b4218eea50f, 707.v71c3f0a. Upgrade to this version or later.
Is CVE-2022-25179 exploitable, and should I be worried? Whether CVE-2022-25179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-25179 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-25179?
- Upgrade org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.26.1 or later
- Upgrade org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.23.1 or later
- Upgrade org.jenkins-ci.plugins.workflow:workflow-multibranch to 696.698.v9b4218eea50f or later
- Upgrade org.jenkins-ci.plugins.workflow:workflow-multibranch to 707.v71c3f0a or later

Other vulnerabilities in org.jenkins-ci.plugins.workflow:workflow-multibranch

CVE-IDSeverityPackage summary

CVE-2022-25175Highorg.jenkins-ci.plugins.workflow:workflow-multibranch: Jenkins Pipeline: Multibranch Plugin vulnerable to OS Command Injection