Jenkins Git server Plugin does not perform a permission checkGHSA-xh9c-vcf9-h94m
MEDIUMGHSA-xh9c-vcf9-h94m is a medium-severity (CVSS 5.3) Improper Privilege Management vulnerability in org.jenkins-ci.plugins:git-server. A fix is available for org.jenkins-ci.plugins:git-server — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xh9c-vcf9-h94m.
EPSS Exploitation Probability
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
org.jenkins-ci.plugins:git-serverReal-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 Git server Plugin 114.v068a_c7cc2574 and earlier does not perform a permission check for read access to a Git repository over SSH.
This allows attackers with a previously configured SSH public key but lacking Overall/Read permission to access Git repositories.
Git server Plugin 117.veb_68868fa_027 requires Overall/Read permission to access Git repositories over SSH.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:git-server | all versions | 117.veborg.jenkins-ci.plugins:git-server:117.veb |
Affected Products
git serverjenkinsDetection & 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:git-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:git-server to 117.veb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xh9c-vcf9-h94m is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-xh9c-vcf9-h94m in your dependencies?
Find it across Maven, including transitive dependencies.