# CVE-2025-58459: Jenkins global-build-stats Plugin missing permission check can result in graph IDs being enumerated

> Attackers with read permissions can enumerate graph IDs due to missing permission checks in the Jenkins global-build-stats plugin REST API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-gm8g-fh49-qq6v

## What is CVE-2025-58459?

CVE-2025-58459 is a medium-severity missing authorization vulnerability in Jenkins global-build-stats Plugin, published on 3 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-58459?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:global-build-stats. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:global-build-stats` | Maven | All versions | 347.v32a |
| `org.jenkins-ci.plugins:global-build-stats` | Maven | All versions | 347.v32a |

Products: Jenkins Global Build Stats.

## How do I fix CVE-2025-58459?

Upgrade org.jenkins-ci.plugins:global-build-stats to 347.v32a or later.

## Is CVE-2025-58459 being exploited?

There is no known exploitation of CVE-2025-58459 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58459 and fix it if it is affected.

What it is: CVE-2025-58459 is a medium-severity missing authorization vulnerability in Jenkins global-build-stats Plugin, published on 3 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58459 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:global-build-stats (Maven): affected all versions; fixed in 347.v32a
- org.jenkins-ci.plugins:global-build-stats (Maven): affected all versions; fixed in 347.v32a

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58459/ (Markdown: https://insights.sbomify.com/CVE-2025-58459/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58459
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58459
- OSV: https://osv.dev/vulnerability/CVE-2025-58459

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58459/
Summaries are generated and may contain mistakes; the official description above is the record.