Org.jenkins ci.main:jenkins core: Jenkins has a missing permission check, allowing users to obtain agent names
Affects org.jenkins-ci.main:jenkins-coreSource GCVE Database
Not known to be exploited · public detection template (Nuclei) · CVSS 5.3 Medium : upgrade to 2.516.3 when convenient.
Data as of 4 Nov 2026, 18:17 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 2.516.3, 2.528
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2025
Detectable: evidence found.
nuclei template: Jenkins Sidepanel - Unauthorized Agent/Queue Exposure
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade org.jenkins-ci.main:jenkins-core to 2.516.3; org.jenkins-ci.main:jenkins-core to 2.528.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.jenkins-ci.main:jenkins-core | Affected
| Fixed in
|
| Mavenorg.jenkins-ci.main:jenkins-core | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official Jenkins updates to versions 2.516.3 or later, or 2.528 or later, which remove the vulnerable sidepanel and enforce proper permission checks. Since a patch is available, upgrading to these fixed versions is the recommended remediation.
Description
Jenkins versions 2.527 and earlier, including LTS 2.516.2 and earlier, have a missing permission check in the sidepanel of a page accessible to users without Overall/Read permission. This flaw allows unauthorized users to list agent names via the sidepanel executors widget. The issue is fixed in Jenkins 2.516.3 and 2.528 by removing the vulnerable sidepanel from the affected view.