# CVE-2026-48921: Jenkins Pipeline: Groovy Libraries Plugin does not prohibit symbolic links in shared libraries

> Attackers controlling shared library content can use symbolic links to read arbitrary files on the Jenkins controller filesystem.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-qjq3-wqj5-g37q

## What is CVE-2026-48921?

CVE-2026-48921 is a high-severity path traversal vulnerability in Jenkins Pipeline: Groovy Libraries Plugin, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier does not prohibit symbolic links in shared libraries, allowing attackers able to control the content of a library used by a Pipeline job to read arbitrary files on the Jenkins controller filesystem.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-48921?

2 open source packages ship an affected version, including io.jenkins.plugins:pipeline-groovy-lib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:pipeline-groovy-lib` | Maven | All versions | 798.v5cc688825312 |
| `io.jenkins.plugins:pipeline-groovy-lib` | Maven | All versions | 798.v5cc688825312 |

Products: Jenkins Pipeline\.

## How do I fix CVE-2026-48921?

Upgrade io.jenkins.plugins:pipeline-groovy-lib to 798.v5cc688825312 or later.

## Is CVE-2026-48921 being exploited?

There is no known exploitation of CVE-2026-48921 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Pipeline: Groovy Libraries Plugin

- [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild)
- [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9)
- [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8)
- [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8)
- [CVE-2022-25173](https://insights.sbomify.com/CVE-2022-25173/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48921 and fix it if it is affected.

What it is: CVE-2026-48921 is a high-severity path traversal vulnerability in Jenkins Pipeline: Groovy Libraries Plugin, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48921 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:pipeline-groovy-lib (Maven): affected all versions; fixed in 798.v5cc688825312
- io.jenkins.plugins:pipeline-groovy-lib (Maven): affected all versions; fixed in 798.v5cc688825312

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48921/ (Markdown: https://insights.sbomify.com/CVE-2026-48921/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48921
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48921
- OSV: https://osv.dev/vulnerability/CVE-2026-48921

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48921/
Summaries are generated and may contain mistakes; the official description above is the record.