CSRF vulnerability and missing permission checks in Jenkins Publish Over SSH PluginGHSA-884c-9wwh-9p6v
MEDIUMFix: jenkinsci/publish-over-ssh-plugin@21bf41aGHSA-884c-9wwh-9p6v is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:publish-over-ssh. EPSS puts its 30-day exploitation probability at 26.5% (98th percentile). A fix is available for org.jenkins-ci.plugins:publish-over-ssh — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-884c-9wwh-9p6v by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.plugins:publish-over-sshReal-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
A cross-site request forgery (CSRF) vulnerability in Jenkins Publish Over SSH Plugin 1.22 and earlier allows attackers to connect to an attacker-specified SSH server using attacker-specified credentials.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:publish-over-ssh | all versions | 1.23org.jenkins-ci.plugins:publish-over-ssh:1.23 |
Affected Products
publish over sshjenkinsDetection & 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:publish-over-ssh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:publish-over-ssh to 1.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-884c-9wwh-9p6v 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.
Frequently Asked Questions
Is GHSA-884c-9wwh-9p6v in your dependencies?
Find it across Maven, including transitive dependencies.