Grafana: Users can generate Service Account tokens after permissions removalGHSA-wfhv-mj62-f5xh
MEDIUMFix: grafana/grafana@fb7336fGHSA-wfhv-mj62-f5xh is a medium-severity (CVSS 5.9) CWE-284 vulnerability in github.com/grafana/grafana. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-wfhv-mj62-f5xh.
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
github.com/grafana/grafanaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
When a user's access to mint tokens for a service account is revoked, it is sometimes still possible to do so for a few seconds after the event. The user will eventually lose access to do this.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/grafana | all versions | 1.9.2-0.20260513165311-fb7336fc36c1go get github.com/grafana/grafana@v1.9.2-0.20260513165311-fb7336fc36c1 |
Affected Products
grafanagrafanaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/grafana to 1.9.2-0.20260513165311-fb7336fc36c1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wfhv-mj62-f5xh 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.
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-wfhv-mj62-f5xh (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | grafana13-1-main-13.1.6-0.1.hum1 | RHSA-2026:68767 |
| Red Hat Hardened Images | grafana13-2-main-13.2.1-0.5.hum1 | RHSA-2026:68778 |
| Red Hat Hardened Images | grafana12-4-main-12.4.10-0.6.hum1 | RHSA-2026:68821 |
Frequently Asked Questions
Is GHSA-wfhv-mj62-f5xh in your dependencies?
Find it across Go, including transitive dependencies.