Jenkins global-build-stats Plugin missing permission check can result in graph IDs being enumeratedGHSA-gm8g-fh49-qq6v
MEDIUMFix: jenkinsci/global-build-stats-plugin@32aeb04GHSA-gm8g-fh49-qq6v is a medium-severity (CVSS 4.3) CWE-284 vulnerability in org.jenkins-ci.plugins:global-build-stats. A fix is available for org.jenkins-ci.plugins:global-build-stats — 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-gm8g-fh49-qq6v.
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:global-build-statsReal-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 global-build-stats Plugin 322.v22f4db_18e2dd and earlier does not perform permission checks in its REST API endpoints, allowing attackers with Overall/Read permission to enumerate graph IDs.
This has been patched in version 347.v32a_eb_0493c4f.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:global-build-stats | all versions | 347.v32aorg.jenkins-ci.plugins:global-build-stats:347.v32a |
Affected Products
global build statsjenkinsDetection & 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:global-build-stats, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:global-build-stats to 347.v32a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm8g-fh49-qq6v is resolved across your whole dependency graph.
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
Is GHSA-gm8g-fh49-qq6v in your dependencies?
Find it across Maven, including transitive dependencies.