Is CVE-2026-48921 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48921 being exploited in the wild.

How severe is CVE-2026-48921?

High severity, with a CVSS score of 7.5, published 27 May 2026.

Which products and versions are affected?

Jenkins Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier; Jenkins Project Pipeline: Groovy Libraries <= 797.v90ea_a_9b_e45a_0; io.jenkins.plugins:pipeline-groovy-lib (Maven) < 798.v5cc688825312, ECOSYSTEM:introduced=0,fixed=798.v5cc688825312.

Is there a fix for CVE-2026-48921?

Yes. io.jenkins.plugins:pipeline-groovy-lib (Maven): upgrade to 798.v5cc688825312 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48921 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48921?

Check whether you run Jenkins Pipeline: Groovy Libraries Plugin, Jenkins Project Pipeline: Groovy Libraries or io.jenkins.plugins:pipeline-groovy-lib (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48921: Jenkins Pipeline: Groovy Libraries Plugin arbitrary file read via symbolic links

Q: Is there a fix for CVE-2026-48921?

Yes. io.jenkins.plugins:pipeline-groovy-lib (Maven): upgrade to 798.v5cc688825312 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48921 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-48921?

Check whether you run Jenkins Pipeline: Groovy Libraries Plugin, Jenkins Project Pipeline: Groovy Libraries or io.jenkins.plugins:pipeline-groovy-lib (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48921 · Severity: high · CVSS 7.5 · Published 2026-05-27

The Jenkins Pipeline: Groovy Libraries Plugin, which allows developers to share code across different automation pipelines, contains a security flaw. An attacker who can modify the code within a shared library can use symbolic links to trick the system into reading sensitive files from the Jenkins server's filesystem. This could lead to the exposure of configuration data, credentials, or other private information stored on the server.

Technologies: Jenkins Pipeline: Groovy Libraries Plugin, io.jenkins.plugins:pipeline-groovy-lib (Maven). Vendors: Jenkins, Jenkins Project, Maven.

Quick answers

Is CVE-2026-48921 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48921 being exploited in the wild.
How severe is CVE-2026-48921?: High severity, with a CVSS score of 7.5, published 27 May 2026.
Which products and versions are affected?: Jenkins Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier; Jenkins Project Pipeline: Groovy Libraries <= 797.v90ea_a_9b_e45a_0; io.jenkins.plugins:pipeline-groovy-lib (Maven) < 798.v5cc688825312, ECOSYSTEM:introduced=0,fixed=798.v5cc688825312.
Is there a fix for CVE-2026-48921?: Yes. io.jenkins.plugins:pipeline-groovy-lib (Maven): upgrade to 798.v5cc688825312 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48921 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48921?: Check whether you run Jenkins Pipeline: Groovy Libraries Plugin, Jenkins Project Pipeline: Groovy Libraries or io.jenkins.plugins:pipeline-groovy-lib (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

io.jenkins.plugins:pipeline-groovy-lib (Maven): upgrade to 798.v5cc688825312 or later

# set io.jenkins.plugins:pipeline-groovy-lib to 798.v5cc688825312 in your pom.xml or build.gradle

Technical details

The Jenkins Pipeline: Groovy Libraries Plugin (versions 797.v90ea_a_9b_e45a_0 and earlier) fails to prohibit or validate symbolic links within shared libraries. This is a 'Link Following' vulnerability (CWE-59). An attacker with the ability to control the content of a library used by a Pipeline job (requiring Low privileges and High attack complexity due to the need for library control) can create a symbolic link pointing to sensitive files on the Jenkins controller's filesystem. When the Pipeline job processes the library, it follows the link, allowing the attacker to read arbitrary files. The issue is resolved in version 798.v5cc688825312.

Affected products

Jenkins Project Pipeline: Groovy Libraries Plugin <= 797.v90ea_a_9b_e45a_0

Identifiers

CVE-2026-48921
GHSA-qjq3-wqj5-g37q

Timeline

2026-05-27: disclosed
2026-05-27: advisory
2026-05-27: patched

References

https://www.jenkins.io/security/advisory/2026-05-27/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.