Jenkins has a missing permission check, allowing users to obtain agent namesGHSA-67v4-38h7-9jjp
MEDIUMGHSA-67v4-38h7-9jjp is a medium-severity (CVSS 5.3) CWE-862 vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-67v4-38h7-9jjp.
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.main:jenkins-core☕org.jenkins-ci.main:jenkins-coreReal-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 2.527 and earlier, LTS 2.516.2 and earlier does not perform a permission check in the sidepanel of a page intentionally accessible to users lacking Overall/Read permission.
This allows attackers without Overall/Read permission to list agent names through its sidepanel executors widget.
Jenkins 2.528, LTS 2.516.3 removes the sidepanel from the affected view.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | all versions | 2.516.3org.jenkins-ci.main:jenkins-core:2.516.3 |
| ☕Maven | org.jenkins-ci.main:jenkins-core | ≥ 2.517&&< 2.528 | 2.528org.jenkins-ci.main:jenkins-core:2.528 |
Affected Products
jenkinsjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.516.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67v4-38h7-9jjp 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.
How to detect GHSA-67v4-38h7-9jjp
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-67v4-38h7-9jjp -u https://target- Template
- Jenkins Sidepanel - Unauthorized Agent/Queue Exposure
- Severity
- medium
- Impact
- Attackers can list agent names without required permissions, potentially exposing sensitive infrastructure details.
- Remediation
- Update to a version later than 2.527 or LTS later than 2.516.2.
Template by ProjectDiscovery nuclei-templates (ivaldivieso), MIT licensed. View the full template. Scan only systems you are authorised to test.
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.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-67v4-38h7-9jjp (CC BY 4.0)
Frequently Asked Questions
Is GHSA-67v4-38h7-9jjp in your dependencies?
Find it across Maven, including transitive dependencies.