Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2022-25179 — workflow-multibranch

MEDIUM

CVE-2022-25179 is a medium-severity (CVSS 6.5) CWE-59 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.

Link Following in Jenkins Pipeline Multibranch Plugin

Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
1.07%1.47%1.88%2.29%1.6%1.8%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2022-25179 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

4 pkgs affected
☕org.jenkins-ci.plugins.workflow:workflow-multibranch☕org.jenkins-ci.plugins.workflow:workflow-multibranch☕org.jenkins-ci.plugins.workflow:workflow-multibranch☕org.jenkins-ci.plugins.workflow:workflow-multibranch

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

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins.workflow:workflow-multibranch≥ 2.24&&< 2.26.12.26.1org.jenkins-ci.plugins.workflow:workflow-multibranch:2.26.1
☕Mavenorg.jenkins-ci.plugins.workflow:workflow-multibranchall versions2.23.1org.jenkins-ci.plugins.workflow:workflow-multibranch:2.23.1
☕Mavenorg.jenkins-ci.plugins.workflow:workflow-multibranch≥ 696.v52535c46f4c9&&< 696.698.v9b4218eea50f696.698.v9b4218eea50forg.jenkins-ci.plugins.workflow:workflow-multibranch:696.698.v9b4218eea50f
☕Mavenorg.jenkins-ci.plugins.workflow:workflow-multibranch≥ 706.vd43c65dec013&&< 707.v71c3f0a707.v71c3f0aorg.jenkins-ci.plugins.workflow:workflow-multibranch:707.v71c3f0a

Affected Products

1 product · 1 configurations
Application
pipeline\jenkins
≤ 706.vd43c65dec013
1 version
_multibranch

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update org.jenkins-ci.plugins.workflow:workflow-multibranch to 2.26.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25179 is resolved across your whole dependency graph.

  3. 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.

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.

Red HatModerate
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.11jenkins-2-plugins-0:3.11.1650371376-1.el7RHSA-2022:1420
Red Hat OpenShift Container Platform 4.10jenkins-2-plugins-0:4.10.1647505461-1.el8RHSA-2022:1025
Red Hat OpenShift Container Platform 4.6jenkins-2-plugins-0:4.6.1650364520-1.el8RHSA-2022:1620
Red Hat OpenShift Container Platform 4.7jenkins-2-plugins-0:4.7.1648800585-1.el8RHSA-2022:1248
Red Hat OpenShift Container Platform 4.8jenkins-2-plugins-0:4.8.1646993358-1.el8RHSA-2022:0871
Red Hat OpenShift Container Platform 4.9jenkins-2-plugins-0:4.9.1647580879-1.el8RHSA-2022:1021

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2022-25179 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2022-25179: workflow-multibranch — Fixed in 2.26.1