NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding PluginGHSA-gqm2-2gcx-p88w

MEDIUMFix: jenkinsci/credentials-binding-plugin@2dd5eda

GHSA-gqm2-2gcx-p88w is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:credentials-binding. A fix is available for org.jenkins-ci.plugins:credentials-binding — see the affected versions and patch details below.

Also known asCVE-2022-20616
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk+0.03%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk
0.00%0.46%0.92%1.38%0.0%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.jenkins-ci.plugins:credentials-binding☕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 prior to 1.27.1 and 1.24.1 does not perform a permission check in a method implementing form validation.

This allows attackers with Overall/Read access to validate if a credential ID refers to a secret file credential and whether it’s a zip file.

Credentials Binding Plugin 1.27.1 and 1.24.1 performs permission checks when validating secret file credentials IDs.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins:credentials-binding≥ 1.25&&< 1.27.11.27.1org.jenkins-ci.plugins:credentials-binding:1.27.1
☕Mavenorg.jenkins-ci.plugins:credentials-bindingall versions1.24.1org.jenkins-ci.plugins:credentials-binding:1.24.1

Affected Products

1 product · 1 configurations
Application
credentials bindingjenkins
≤ 1.27
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:credentials-binding, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins:credentials-binding to 1.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqm2-2gcx-p88w is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Jenkins Credentials Binding Plugin prior to 1.27.1 and 1.24.1 does not perform a permission check in a method implementing form validation. This allows attackers with Overall/Read access to validate if a credential ID refers to a secret file credential and whether it’s a zip file. Credentials Binding Plugin 1.27.1 and 1.24.1 performs permission checks when validating secret file credentials IDs.
O3 Security · Impact-Aware SCA

Is GHSA-gqm2-2gcx-p88w in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Incorrect Permission Assignment for Critical Resource in…