How severe is CVE-2019-10357?

CVE-2019-10357 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-2019-10357?

CVE-2019-10357 affects the following packages: org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10357?

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

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

How do I mitigate CVE-2019-10357 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2019-10357 actively exploited in the wild?

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

CVE-2019-10357 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th 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-2019-10357?

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

When was CVE-2019-10357 published, and has it been updated?

CVE-2019-10357 was published on July 31, 2019 and was last updated on October 24, 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-2019-10357 — workflow-cps-global-lib

MEDIUMFix: jenkinsci/workflow-cps-global-lib-plugin@6fce1e2

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

Missing Authorization in Jenkins Pipeline: Shared Groovy Libraries Plugin

Also known asGHSA-9x5v-8352-244g

Published

Jul 31, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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

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 missing permission check in Jenkins Pipeline: Shared Groovy Libraries Plugin 2.14 and earlier allowed users with Overall/Read access to obtain limited information about the content of SCM repositories referenced by global libraries.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 3 configurations

Application

pipeline\jenkins

≤ 2.14

1 version

shared_groovy_libraries

Application

openshift container platformredhat

2 versions

3.114.1

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-global-lib, 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-global-lib to 2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10357 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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.1566492396-1.el7`	RHSA-2019:2651
Red Hat OpenShift Container Platform 4.1	`jenkins-2-plugins-0:4.1.1567707934-1.el7`	RHSA-2019:2662

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-10357 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-862CWE-862

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jul 31, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-10357

GHSA-9x5v-8352-244g

References

Advisoryopenwall.com Advisoryaccess.redhat.com · RHSA 2019:2594 Advisoryaccess.redhat.com · RHSA 2019:2651 Advisoryaccess.redhat.com · RHSA 2019:2662 Advisoryjenkins.io · 2019 07 31 Advisorynvd.nist.gov · CVE 2019 10357 Webgithub.com · 6fce1e241d82641e8648c546bc63c22a5e07e96b Packagegithub.com · workflow cps global lib plugin

Related vulnerabilities

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

CVE-2022-43405CVE-2022-43406CVE-2022-29047CVE-2022-25178CVE-2022-25182CVE-2022-25181CVE-2022-25174CVE-2022-25183

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-10357 — workflow-cps-global-lib

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-2019-10357 in your dependencies?