JenkinsApplication
CVE-2025-59474
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins versions 2.527 and earlier, and LTS 2.516.2 and earlier fail to perform a permission check in the sidepanel of a page intentionally accessible to users lacking Overall/Read permission. The sidepanel executors widget exposes agent/node names to unauthorized users, creating an information disclosure vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenkinsApplication
< 2.516.3< 2.528CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Jenkins versionNavigate to Manage Jenkins > About Jenkins, or access /api/json?tree=version to retrieve the version number. Compare against affected ranges: less than 2.528 for weekly releases, or less than 2.516.3 for LTS releases.Affected if Version is 2.527 or earlier for weekly releases, or 2.516.2 or earlier for LTS releases.
-
Verify if anonymous or low-privilege access is enabledNavigate to Manage Jenkins > Manage Users. Check if anonymous access is enabled under Manage Jenkins > Configure Global Security. Look for authorization settings that allow access to users without Overall/Read permission.Affected if Anonymous access is enabled, or users/groups are granted access without having Overall/Read permission.
-
Check for configured agents or nodesNavigate to Manage Jenkins > Nodes or Manage Jenkins > Manage Nodes. Observe if any agents or nodes are configured in the Jenkins environment.Affected if Any agents or nodes are configured in the Jenkins instance.
-
Verify sidepanel accessibility for unauthorized usersLog in as a user without Overall/Read permission, or access the Jenkins dashboard anonymously. Inspect the sidepanel (typically the left-hand navigation area) to see if agent/node names are visible in the executors widget.Affected if Agent or node names are displayed in the sidepanel to users lacking Overall/Read permission.
The environment is affected if running Jenkins version 2.527 or earlier (weekly) or 2.516.2 or earlier (LTS), anonymous or low-privilege access is enabled, agents or nodes exist, and the sidepanel displays node/agent names to unauthorized users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.516.32.528
Upgrade Jenkins to version 2.527.1 or LTS 2.516.3 to apply the security fix. Ensure that the upgrade is tested in a staging environment before production deployment.
Jenkins 2.528 (weekly) or Jenkins LTS 2.516.3
- Backup your Jenkins configuration and data
- Schedule a maintenance window for the upgrade
- Upgrade Jenkins to version 2.528 (weekly) or LTS 2.516.3
- Restart Jenkins to apply the update
- Verify the upgrade was successful by logging in
- Confirm the permission check now properly restricts access to agent names for users without Overall/Read permission
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59474 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data