# CVE-2026-42520: Jenkins Credentials Binding Plugin has a path traversal vulnerability

Source: https://junglewise.ai/threats/cve-2026-42520-jenkins-credentials-binding-plugin-has-a-path-traversal  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-29  
License: CC BY 4.0 with a link back

CVE-2026-42520 · Severity: high · CVSS 7.5 · Published 2026-04-29

Jenkins Credentials Binding Plugin 719.v80e905ef14eb_ and earlier does not 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.

Technologies: [org.jenkins-ci.plugins:credentials-binding (Maven)](https://junglewise.ai/threats/technologies/org-jenkins-ci-plugins-credentials-binding). Vendors: [Jenkins](https://junglewise.ai/threats/vendors/jenkins), [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2026-42520 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-42520 being exploited in the wild.

**How severe is CVE-2026-42520?** High severity, with a CVSS score of 7.5, published 29 April 2026.

**Which products and versions are affected?** org.jenkins-ci.plugins:credentials-binding (Maven) ECOSYSTEM:introduced=0,fixed=720.v3f6decef43ea.

**Is there a fix for CVE-2026-42520?** Yes. org.jenkins-ci.plugins:credentials-binding (Maven): upgrade to 720.v3f6decef43ea or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-42520?** Check whether you run Jenkins Credentials Binding or org.jenkins-ci.plugins:credentials-binding (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

- org.jenkins-ci.plugins:credentials-binding (Maven): upgrade to 720.v3f6decef43ea or later

  ```sh
  # set org.jenkins-ci.plugins:credentials-binding to 720.v3f6decef43ea in your pom.xml or build.gradle
  ```


## Affected products

- Jenkins Credentials Binding
- org.jenkins-ci.plugins:credentials-binding (Maven) ECOSYSTEM:introduced=0,fixed=720.v3f6decef43ea

## Identifiers

- CVE-2026-42520
- GHSA-p2rf-wpxj-mx2g

## Related threats

- [Jenkins Credentials Binding Plugin path traversal in file credentials](https://junglewise.ai/threats/cve-2026-48922-jenkins-credentials-binding-plugin-path-traversal-in-file)
- [Jenkins Credentials Binding Plugin vulnerability can expose sensitive information in logger messages](https://junglewise.ai/threats/cve-2025-53650-jenkins-credentials-binding-plugin-vulnerability-can-expose)
- [Improper masking of some secrets in Jenkins Credentials Binding Plugin](https://junglewise.ai/threats/cve-2020-2182-improper-masking-of-some-secrets-in-jenkins-credentials-binding)
- [Secrets are not masked by Jenkins Credentials Binding Plugin in builds without build steps](https://junglewise.ai/threats/cve-2020-2181-secrets-are-not-masked-by-jenkins-credentials-binding-plugin-in)
- [Jenkins Credentials Binding Plugin Stores Passwords in a Recoverable Format](https://junglewise.ai/threats/cve-2019-1010241-jenkins-credentials-binding-plugin-stores-passwords-in-a)