How severe is CVE-2022-25180?

CVE-2022-25180 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-25180?

CVE-2022-25180 affects the following packages: org.jenkins-ci.plugins.workflow:workflow-cps (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-25180?

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

How do I detect CVE-2022-25180 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-25180 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 CVE-2022-25180 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-25180 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 CVE-2022-25180?

CVE-2022-25180 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th 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 CVE-2022-25180?

CVE-2022-25180 is classified as CWE-319 (CWE-319). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-25180 published, and has it been updated?

CVE-2022-25180 was published on February 15, 2022 and was last updated on July 9, 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

MEDIUM severity

CVE-2022-25180 — workflow-cps

MEDIUMFix: jenkinsci/workflow-cps-plugin@886676e

CVE-2022-25180 is a medium-severity (CVSS 4.3) CWE-319 vulnerability in org.jenkins-ci.plugins.workflow:workflow-cps. A fix is available for org.jenkins-ci.plugins.workflow:workflow-cps — see the affected versions and patch details below.

Jenkins Pipeline: Groovy Plugin has Insufficiently Protected Credentials

Also known asGHSA-qv6q-x9vr-w7j3

Published

Feb 15, 2022

Updated

Jul 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 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 CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

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

How urgent is this, really

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

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

Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier includes password parameters from the original build in replayed builds.

This allows attackers with Run/Replay permission to obtain the values of password parameters passed to previous builds of a Pipeline.

Pipeline: Groovy Plugin 2656.vf7a_e7b_75a_457 does not allow builds containing password parameters to be replayed.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

pipeline\jenkins

≤ 2648.va9433432b33c

1 version

_groovy

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins.workflow:workflow-cps to 2656.vf7a_e7b_75a_457 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25180 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.

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

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

Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier includes password parameters from the original build in replayed builds. This allows attackers with Run/Replay permission to obtain the values of password parameters passed to previous builds of a Pipeline. Pipeline: Groovy Plugin 2656.vf7a_e7b_75a_457 does not allow builds containing password parameters to be replayed.

O3 Security · Impact-Aware SCA

Is CVE-2022-25180 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-319CWE-319

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 15, 2022

Last updated

Jul 9, 2026

Identifiers

CVE-2022-25180

GHSA-qv6q-x9vr-w7j3

References

Advisorynvd.nist.gov Fixjenkins.io Webgithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting workflow-cps are rated as high or higher (top: critical).

CVE-2024-52550CVE-2022-43404CVE-2022-43401CVE-2022-43402CVE-2020-2109CVE-2022-30945CVE-2018-1000866CVE-2017-1000096

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 9, 2026

CVE-2022-25180 — workflow-cps

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-25180 in your dependencies?