How severe is CVE-2022-43405?

CVE-2022-43405 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-43405?

CVE-2022-43405 affects the following packages: io.jenkins.plugins:pipeline-groovy-lib (Maven), org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-43405?

Update io.jenkins.plugins:pipeline-groovy-lib to 613.v9c41a_160233f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43405 is resolved across your whole dependency graph.

How do I detect CVE-2022-43405 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:pipeline-groovy-lib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

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

CVE-2022-43405 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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.

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

CVE-2022-43405 was published on October 19, 2022 and was last updated on November 8, 2023. 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

HIGH severity

CVE-2022-43405 — pipeline-groovy-lib

HIGH

CVE-2022-43405 is a high-severity (CVSS 8.8) remote code execution vulnerability in io.jenkins.plugins:pipeline-groovy-lib. A fix is available for io.jenkins.plugins:pipeline-groovy-lib — see the affected versions and patch details below.

Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Libraries Plugin and Pipeline: Deprecated Groovy Libraries Plugin

Published

Oct 19, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs74th percentile — riskier than 74% 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

2 pkgs affected

☕io.jenkins.plugins:pipeline-groovy-lib☕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

Pipeline: Groovy Libraries Plugin and older releases of the Pipeline: Deprecated Groovy Libraries Plugin (formerly Pipeline: Shared Groovy Libraries Plugin) define the library Pipeline step, which allows Pipeline authors to dynamically load Pipeline libraries. The return value of this step can be used to instantiate classes defined in the loaded library.

In Pipeline: Groovy Libraries Plugin 612.v84da_9c54906d and earlier and in Pipeline: Deprecated Groovy Libraries Plugin 583.vf3b_454e43966 and earlier, the library step can be used to invoke sandbox-generated synthetic constructors in crafted untrusted libraries and construct any subclassable type. This is similar to SECURITY-582 in the 2017-08-07 security advisory, but in a different plugin.

This vulnerability allows attackers with permission to define untrusted Pipeline libraries and to define and run sandboxed Pipelines, to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.

Pipeline: Groovy Libraries Plugin 613.v9c41a_160233f rejects improper calls to sandbox-generated synthetic constructors when using the library step.

Pipeline: Deprecated Groovy Libraries Plugin 588.v576c103a_ff86 no longer contains the library step. It has been moved into the Pipeline: Groovy Libraries Plugin.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:pipeline-groovy-lib`	all versions	613.v9c41a_160233f`io.jenkins.plugins:pipeline-groovy-lib:613.v9c41a_160233f`
☕Maven	`org.jenkins-ci.plugins.workflow:workflow-cps-global-lib`	all versions	588.v576c103a_ff86`org.jenkins-ci.plugins.workflow:workflow-cps-global-lib:588.v576c103a_ff86`

Affected Products

1 product · 1 configurations

Application

groovy librariesjenkins

≤ 612.v84da_9c54906d

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:pipeline-groovy-lib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:pipeline-groovy-lib to 613.v9c41a_160233f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-43405 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 HatCritical

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-2-plugins-0:4.12.1675702407-1.el8`	RHSA-2023:1064
OpenShift Developer Tools and Services for OCP 4.11	`jenkins-2-plugins-0:4.11.1683009941-1.el8`	RHSA-2023:3198
Red Hat OpenShift Container Platform 4.10	`jenkins-2-plugins-0:4.10.1675144701-1.el8`	RHSA-2023:0560
Red Hat OpenShift Container Platform 4.9	`jenkins-2-plugins-0:4.9.1675668922-1.el8`	RHSA-2023:0777

Frequently Asked Questions

Pipeline: Groovy Libraries Plugin and older releases of the Pipeline: Deprecated Groovy Libraries Plugin (formerly Pipeline: Shared Groovy Libraries Plugin) define the l`ibrary` Pipeline step, which allows Pipeline authors to dynamically load Pipeline libraries. The return value of this step can be used to instantiate classes defined in the loaded library. In Pipeline: Groovy Libraries Plugin 612.v84da_9c54906d and earlier and in Pipeline: Deprecated Groovy Libraries Plugin 583.vf3b_454e43966 and earlier, the `library` step can be used to invoke sandbox-generated synthetic constructors in cra

O3 Security · Impact-Aware SCA

Is CVE-2022-43405 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

Weaponization

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

Timeline

Disclosed

Oct 19, 2022

Last updated

Nov 8, 2023

Identifiers

CVE-2022-43405

References

Advisorynvd.nist.gov · CVE 2022 43405 Webjenkins.io · 2022 10 19 Webopenwall.com

Related vulnerabilities

Also affects pipeline-groovy-lib

This CVE is high severity; 2 of 4 other CVEs affecting pipeline-groovy-lib are rated as high or higher (top: high).

CVE-2026-57284CVE-2026-57283CVE-2026-48921CVE-2022-43406

Also affects workflow-cps-global-lib

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

CVE-2019-10357CVE-2022-29047CVE-2022-25178CVE-2022-25182

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023

CVE-2022-43405 — pipeline-groovy-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-2022-43405 in your dependencies?