# CVE-2026-48922: Jenkins Credentials Binding Plugin does not properly sanitize file names for file and zip file credentials

> Attackers can write files to arbitrary locations via unsanitized credential names, potentially achieving remote code execution on Jenkins nodes.

- **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-fxxf-w25w-mcx2

## What is CVE-2026-48922?

CVE-2026-48922 is a high-severity path traversal vulnerability in Jenkins Credentials Binding 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 Credentials Binding Plugin 720.v3f6decef43ea_ and earlier does not properly sanitize file names for file and zip file credentials, allowing attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem, which can lead to remote code execution if Jenkins is configured to allow a low-privileged user to configure file or zip file credentials used for a job running on the built-in node.

Weakness: CWE-20 (Improper Input Validation)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:credentials-binding. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:credentials-binding` | Maven | All versions | 725.ve52b |
| `org.jenkins-ci.plugins:credentials-binding` | Maven | All versions | 725.ve52b |

Products: Jenkins Credentials Binding.

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

Upgrade org.jenkins-ci.plugins:credentials-binding to 725.ve52b or later.

## Is CVE-2026-48922 being exploited?

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

## Other vulnerabilities in Jenkins Credentials Binding Plugin

- [CVE-2026-42520](https://insights.sbomify.com/CVE-2026-42520/): Jenkins Credentials Binding Plugin has a path traversal vulnerability (high 7.5)
- [CVE-2025-53650](https://insights.sbomify.com/CVE-2025-53650/): Jenkins Credentials Binding Plugin vulnerability can expose sensitive information in logger messages (high 7.3)
- [CVE-2020-2181](https://insights.sbomify.com/CVE-2020-2181/): Secrets are not masked by Jenkins Credentials Binding Plugin in builds without build steps (medium 6.5)
- [CVE-2019-1010241](https://insights.sbomify.com/CVE-2019-1010241/): Jenkins Credentials Binding Plugin Stores Passwords in a Recoverable Format (medium 6.5)
- [CVE-2022-20616](https://insights.sbomify.com/CVE-2022-20616/): Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48922 is a high-severity path traversal vulnerability in Jenkins Credentials Binding 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-48922 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:credentials-binding (Maven): affected all versions; fixed in 725.ve52b
- org.jenkins-ci.plugins:credentials-binding (Maven): affected all versions; fixed in 725.ve52b

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-48922/ (Markdown: https://insights.sbomify.com/CVE-2026-48922/index.md)
```

## Sources

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

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