Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-59474

jenkins: Missing permission check allows obtaining agent names

Overview

Published
17 Sep 2025
Modified
17 Jun 2026
Medium CVE
2 Registry packages
3 OS packages
4 Linux distributions
Yes Fix available

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, allowing attackers without Overall/Read permission to list agent names through its sidepanel executors widget.

Source: OX vulnerability database

Severity

5.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Weakness: CWE-862

Affected packages · 2

Packages affected by CVE-2025-59474
EcosystemPackageVulnerableFixed in
Bitnami jenkins <2.516.3>=2.517.0, <2.528.0 2.516.32.528.0
Maven org.jenkins-ci.main:jenkins-core <2.516.3>=2.517, <2.528 2.516.32.528

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

alpine 1 release · 1 package

fixed 1
jenkins
alpine fixes for CVE-2025-59474
ReleasePackageFixed in
edge jenkins 2.528.3-r0

chainguard 1 release · 2 packages

fixed 2
jenkins-2-516 jenkins-2
chainguard fixes for CVE-2025-59474
ReleasePackageFixed in
jenkins-2-516 2.516.3-r0
jenkins-2 2.528-r0

minimos 1 release · 1 package

fixed 1
jenkins
minimos fixes for CVE-2025-59474
ReleasePackageFixed in
jenkins 2.528-r0

wolfi 1 release · 1 package

fixed 1
jenkins-2
wolfi fixes for CVE-2025-59474
ReleasePackageFixed in
jenkins-2 2.528-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.