Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-wfhv-mj62-f5xh

MEDIUMFix: grafana/grafana@fb7336f

GHSA-wfhv-mj62-f5xh is a medium-severity (CVSS 5.9) vulnerability in github.com/grafana/grafana. O3 Security confirms whether GHSA-wfhv-mj62-f5xh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Grafana: Users can generate Service Account tokens after permissions removal

Also known asBIT-grafana-2026-33381CVE-2026-33381GO-2026-5708
Published
May 13, 2026
Updated
Jun 25, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/grafana/grafana

Real-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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafanaall versions1.9.2-0.20260513165311-fb7336fc36c1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-wfhv-mj62-f5xh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wfhv-mj62-f5xh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-wfhv-mj62-f5xh in your dependencies?

O3 detects GHSA-wfhv-mj62-f5xh across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.