Skip to content

← Actionable
Critical, CVSS 10.0

Grafana Incorrect Privilege Assignment vulnerability

CVE-2025-41115GHSA-w62r-7c53-fmc5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/grafana/grafana 12.2.2, 12.1.4, 12.0.7, 1.9.2-0.20251106142618-ca5d89812015), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/grafana/grafana

    Affected
    >= 12.0.0, < 12.0.7>= 12.1.0, < 12.1.4>= 12.2.0, < 12.2.2>= 1.9.2-0.20250310110405-e6fdb746f235, < 1.9.2-0.20251106142618-ca5d89812015
    Fixed in
    1.9.2-0.20251106142618-ca5d89812015, 12.1.4, 12.0.7, 12.2.2

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-w62r-7c53-fmc5 lists affected ranges: Go github.com/grafana/grafana >=12.0.0 =12.1.0 =12.2.0 =1.9.2-0.20250310110405-e6fdb746f235 <1.9.2-0.20251106142618-ca5d89812015

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2025-41115: 17.50% estimated exploitation activity in the next 30 days; percentile 97.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 - usersyncenabled config option in the [auth.scim] block set to true

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-w62r-7c53-fmc5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-41115

Advisory: Grafana Incorrect Privilege Assignment vulnerability
IDs: CVE-2025-41115, GHSA-w62r-7c53-fmc5
Record: https://patchnext.com/advisories/cve-2025-41115 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/grafana 12.2.2, 12.1.4, 12.0.7, 1.9.2-0.20251106142618-ca5d89812015. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/grafana: affected >= 12.0.0, < 12.0.7; >= 12.1.0, < 12.1.4; >= 12.2.0, < 12.2.2; >= 1.9.2-0.20250310110405-e6fdb746f235, < 1.9.2-0.20251106142618-ca5d89812015; fixed in 1.9.2-0.20251106142618-ca5d89812015, 12.1.4, 12.0.7, 12.2.2

## Suggested inspection (read-only)
- Go github.com/grafana/grafana: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/grafana/grafana.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w62r-7c53-fmc5 (GitHub-reviewed advisory GHSA-w62r-7c53-fmc5 lists affected ranges: Go github.com/grafana/grafana >=12.0.0 =12.1.0 =12.2.0 =1.9.2-0.20250310110405-e6fdb746f235 <1.9.2-0.20251106142618-ca5d89812015)

Commands are suggestions: review each one before running it.

Loading voting…