GHSA-gchq-9r68-6jwv is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:credentials. EPSS puts its 30-day exploitation probability at 11.3% (96th percentile). A fix is available for org.jenkins-ci.plugins:credentials — see the affected versions and patch details below.
Cross-Site Request Forgery in Jenkins Credentials Plugin
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-gchq-9r68-6jwv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkins-ci.plugins:credentials☕org.jenkins-ci.plugins:credentials☕org.jenkins-ci.plugins:credentials☕org.jenkins-ci.plugins:credentials☕org.jenkins-ci.plugins:credentials☕org.jenkins-ci.plugins:credentialsReal-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 Plugin prior to 2.3.19, 2.3.15.1, 2.3.14.1, 2.3.13.1, 2.3.7.1, and 2.3.0.1 does not escape user-controlled information on a view it provides, resulting in a reflected cross-site scripting (XSS) vulnerability.
Jenkins Credentials Plugin 2.3.19, 2.3.15.1, 2.3.14.1, 2.3.13.1, 2.3.7.1, and 2.3.0.1 restricts the user-controlled information it provides to a safe subset.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:credentials | ≥ 2.3.16&&< 2.3.19 | 2.3.19org.jenkins-ci.plugins:credentials:2.3.19 |
| ☕Maven | org.jenkins-ci.plugins:credentials | ≥ 2.3.15&&< 2.3.15.1 | 2.3.15.1org.jenkins-ci.plugins:credentials:2.3.15.1 |
| ☕Maven | org.jenkins-ci.plugins:credentials | ≥ 2.3.14&&< 2.3.14.1 | 2.3.14.1org.jenkins-ci.plugins:credentials:2.3.14.1 |
| ☕Maven | org.jenkins-ci.plugins:credentials | ≥ 2.3.8&&< 2.3.13.1 | 2.3.13.1org.jenkins-ci.plugins:credentials:2.3.13.1 |
| ☕Maven | org.jenkins-ci.plugins:credentials | ≥ 2.3.1&&< 2.3.7.1 | 2.3.7.1org.jenkins-ci.plugins:credentials:2.3.7.1 |
| ☕Maven | org.jenkins-ci.plugins:credentials | all versions | 2.3.0.1org.jenkins-ci.plugins:credentials:2.3.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:credentials, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:credentials to 2.3.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gchq-9r68-6jwv 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gchq-9r68-6jwv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gchq-9r68-6jwv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.8 | jenkins-2-plugins-0:4.8.1624022417-1.el8 | RHSA-2021:2437 |
Frequently Asked Questions
Is GHSA-gchq-9r68-6jwv in your dependencies?
O3 Security finds GHSA-gchq-9r68-6jwv across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.