How severe is CVE-2022-25183?

CVE-2022-25183 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-25183 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-25183?

CVE-2022-25183 affects Jenkins Pipeline. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-25183?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-25183 published?

CVE-2022-25183 was published on 2022-02-15 and last updated on 2026-06-17.

CVE-2022-25183

CVE-2022-25183 is a high-severity vulnerability in Jenkins Pipeline with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 2% (72nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jenkins Pipeline
Published: 2022-02-15
Last modified: 2026-06-17

Description

Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create cache directories without any sanitization, allowing attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM using specially crafted library names if a global Pipeline library configured to use caching already exists.

Frequently asked questions

What is CVE-2022-25183?: Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create cache directories without any sanitization, allowing attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM using specially crafted library names if a global Pipeline library configured to use caching already exists.
How severe is CVE-2022-25183?: CVE-2022-25183 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-25183 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-25183?: CVE-2022-25183 affects Jenkins Pipeline. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-25183?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-25183 published?: CVE-2022-25183 was published on 2022-02-15 and last updated on 2026-06-17.

References

https://www.jenkins.io/security/advisory/2022-02-15/#SECURITY-2586

Affected products (1)

cpe:2.3:a:jenkins:pipeline\:shared_groovy_libraries:*:*:*:*:*:jenkins:*:*