How severe is GHSA-w62r-7c53-fmc5?

GHSA-w62r-7c53-fmc5 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w62r-7c53-fmc5?

GHSA-w62r-7c53-fmc5 affects the following packages: github.com/grafana/grafana (Go), github.com/grafana/grafana (Go), github.com/grafana/grafana (Go), github.com/grafana/grafana (Go). Ecosystems affected: Go.

How do I fix GHSA-w62r-7c53-fmc5?

Update github.com/grafana/grafana to 12.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w62r-7c53-fmc5 is resolved across your whole dependency graph.

How do I detect GHSA-w62r-7c53-fmc5 in my Go dependencies?

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.

How do I mitigate GHSA-w62r-7c53-fmc5 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-w62r-7c53-fmc5?

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

Is GHSA-w62r-7c53-fmc5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w62r-7c53-fmc5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w62r-7c53-fmc5?

GHSA-w62r-7c53-fmc5 has an EPSS (Exploit Prediction Scoring System) score of 17.3%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-w62r-7c53-fmc5?

GHSA-w62r-7c53-fmc5 is classified as CWE-266 (CWE-266). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w62r-7c53-fmc5 published, and has it been updated?

GHSA-w62r-7c53-fmc5 was published on November 21, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-w62r-7c53-fmc5

CRITICAL

Grafana Incorrect Privilege Assignment vulnerability

Also known asBIT-grafana-2025-41115CVE-2025-41115GO-2025-4153

Published

Nov 21, 2025

Updated

Feb 4, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

17.3%probability of exploitation in next 30 days

Moderate Risk97th percentile+17.24%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹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

SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management.

In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric externalId, which in turn could allow to override internal user IDs and lead to impersonation or privilege escalation.

This vulnerability applies only if all of the following conditions are met:

enableSCIM feature flag set to true
user_sync_enabled config option in the [auth.scim] block set to true

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/grafana/grafana`	≥ 12.0.0&&< 12.0.7	12.0.7
🐹Go	`github.com/grafana/grafana`	≥ 12.1.0&&< 12.1.4	12.1.4
🐹Go	`github.com/grafana/grafana`	≥ 12.2.0&&< 12.2.2	12.2.2
🐹Go	`github.com/grafana/grafana`	≥ 1.9.2-0.20250310110405-e6fdb746f235&&< 1.9.2-0.20251106142618-ca5d89812015	1.9.2-0.20251106142618-ca5d89812015

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update github.com/grafana/grafana to 12.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w62r-7c53-fmc5 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-w62r-7c53-fmc5 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-w62r-7c53-fmc5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

SCIM provisioning was introduced in Grafana Enterprise and Grafana Cloud in April to improve how organizations manage users and teams in Grafana by introducing automated user lifecycle management. In Grafana versions 12.x where SCIM provisioning is enabled and configured, a vulnerability in user identity handling allows a malicious or compromised SCIM client to provision a user with a numeric externalId, which in turn could allow to override internal user IDs and lead to impersonation or privilege escalation. This vulnerability applies only if all of the following conditions are met: - `enab

O3 Security · Impact-Aware SCA

Is GHSA-w62r-7c53-fmc5 in your dependencies?

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

Scan my dependencies How O3 SCA works