How severe is GHSA-p2rf-wpxj-mx2g?

GHSA-p2rf-wpxj-mx2g has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-p2rf-wpxj-mx2g?

GHSA-p2rf-wpxj-mx2g affects the following packages: org.jenkins-ci.plugins:credentials-binding (Maven). Ecosystems affected: Maven.

How do I fix GHSA-p2rf-wpxj-mx2g?

Update org.jenkins-ci.plugins:credentials-binding to 720.v3f6decef43ea or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2rf-wpxj-mx2g is resolved across your whole dependency graph.

How do I detect GHSA-p2rf-wpxj-mx2g in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:credentials-binding. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-p2rf-wpxj-mx2g if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-p2rf-wpxj-mx2g?

O3 pinpoints whether GHSA-p2rf-wpxj-mx2g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p2rf-wpxj-mx2g actively exploited in the wild?

No public exploit code has been indexed for GHSA-p2rf-wpxj-mx2g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p2rf-wpxj-mx2g published, and has it been updated?

GHSA-p2rf-wpxj-mx2g was published on April 29, 2026 and was last updated on May 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-p2rf-wpxj-mx2g

HIGH

GHSA-p2rf-wpxj-mx2g is a high-severity (CVSS 7.5) remote code execution vulnerability in org.jenkins-ci.plugins:credentials-binding. O3 Security confirms whether GHSA-p2rf-wpxj-mx2g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Jenkins Credentials Binding Plugin has a path traversal vulnerability

Also known asCVE-2026-42520

Published

Apr 29, 2026

Updated

May 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 6, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:credentials-binding

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Credentials Binding Plugin versions 719.v80e905ef14eb_ and earlier do not sanitize file names for file and zip file credentials.

This allows attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem. 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, this can lead to remote code execution.

Credentials Binding Plugin 720.v3f6decef43ea_ sanitizes the file name provided for file and zip file credentials, preventing path traversal.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:credentials-binding`	all versions	720.v3f6decef43ea

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:credentials-binding. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins:credentials-binding to 720.v3f6decef43ea or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2rf-wpxj-mx2g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-p2rf-wpxj-mx2g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-p2rf-wpxj-mx2g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jenkins Credentials Binding Plugin versions 719.v80e905ef14eb_ and earlier do not sanitize file names for file and zip file credentials. This allows attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem. 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, this can lead to remote code execution. Credentials Binding Plugin 720.v3f6decef43ea_ sanitizes the file name provided for file and zip file credentials, preventing path traversal.

O3 Security · Impact-Aware SCA

Is GHSA-p2rf-wpxj-mx2g in your dependencies?

O3 detects GHSA-p2rf-wpxj-mx2g across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works