# Jenkins Credentials Binding Plugin has a path traversal vulnerability

Advisory record · `GHSA-p2rf-wpxj-mx2g`

- **Identifiers:** `GHSA-p2rf-wpxj-mx2g` · `CVE-2026-42520`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 29 Apr 2026
- **Updated:** 6 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Apr 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.plugins:credentials-binding` (Maven): affected `<720.v3f6decef43ea`; fixed in `720.v3f6decef43ea`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jenkins Credentials Binding Plugin versions 719.v80e905ef14eb\_ and earlier do not sanitize file names for file and zip file credentials. An attacker who can supply credentials for a job can write files to arbitrary locations on the node filesystem, which can lead to remote code execution if a low-privileged user is allowed to configure such credentials for a job running on the built-in node. Upgrade to version 720.v3f6decef43ea or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0041, the 35th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p2rf-wpxj-mx2g)

## Sources

- [GitHub Advisory Database: GHSA-p2rf-wpxj-mx2g](https://github.com/advisories/GHSA-p2rf-wpxj-mx2g)
- [OSV: GHSA-p2rf-wpxj-mx2g](https://osv.dev/vulnerability/GHSA-p2rf-wpxj-mx2g)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-42520>
- <https://github.com/jenkinsci/credentials-binding-plugin>
- <https://www.jenkins.io/security/advisory/2026-04-29/#SECURITY-3672>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-p2rf-wpxj-mx2g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p2rf-wpxj-mx2g/>. Everything for agents: <https://agentprime.io/llms.txt>.