dbcve.org
GrafanaApplication

CVE-2025-41115

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-21
Fix available
A fix is available. Upgrade to 12.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Grafana 12.x with SCIM provisioning enabled, a vulnerability in user identity handling allows malicious SCIM clients to provision users with numeric externalId values, which can override internal user IDs and enable impersonation or privilege escalation.

MitigationDisable SCIM provisioning by setting the `enableSCIM` feature flag to false or setting `user_sync_enabled` to false in the `[auth.scim]` configuration block until an official patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 12.0.0, < 12.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Grafana version
    Run `grafana-server -v` or look in the Grafana UI at Admin > Stats, or check the version in the `/usr/share/grafana/version` file or RPM/Deb package metadata
    Affected if Version is 12.0.0 or higher but lower than 12.2.1
  2. Verify SCIM provisioning is enabled
    Check the Grafana configuration file (usually grafana.ini or defaults.ini) for `[auth.scim]` section and look for `enableSCIM=true` or `user_sync_enabled=true`
    Affected if SCIM provisioning is enabled in the configuration
  3. Check for SCIM feature flag
    Inspect the Grafana configuration for `enableSCIM` feature flag under `[feature_toggles]` or as an environment variable `GF_FEATURE_TOGGLES_ENABLE_SCIM`
    Affected if The SCIM feature flag is set to true
  4. Inspect user provisioning configuration
    Review the `[auth.scim]` configuration block in grafana.ini to confirm user synchronization is active
    Affected if User sync is enabled in the SCIM configuration block

A system is affected if Grafana version is 12.0.0 through 12.2.0 and SCIM provisioning is enabled via configuration or feature flag.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.2.1 or later
Fixed in 12.2.1
Interim mitigation

Disable SCIM provisioning by setting the `enableSCIM` feature flag to false or setting `user_sync_enabled` to false in the `[auth.scim]` configuration block until an official patch is applied.

Recommended fix High confidence

Grafana 12.2.1 or later

  1. 1. Identify current Grafana version by running `grafana-server --version` or checking the UI at Administration > Stats
  2. 2. Confirm SCIM is enabled by checking for `enableSCIM = true` in feature flags and `user_sync_enabled = true` in `[auth.scim]` configuration section
  3. 3. Backup Grafana database and configuration files before upgrading
  4. 4. Upgrade Grafana to version 12.2.1 or later using your package manager or deployment method (e.g., apt-get upgrade grafana, docker pull grafana/grafana:12.2.1, or helm upgrade)
  5. 5. Verify the upgrade was successful and Grafana starts without errors
  6. 6. Test SCIM user provisioning functionality to ensure it continues to work as expected after the security update
Caveat Review Grafana 12.1.x and 12.2.x release notes for any breaking changes before upgrading, though this is primarily a security patch release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41115 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data