# CVE-2026-92539: Cross-organization user modification and deletion via the SCIM API in Grafana Enterprise


- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** BIT-grafana-2026-92539, GHSA-9vhw-jmv9-mgm3

## What is CVE-2026-92539?

CVE-2026-92539 is a medium-severity vulnerability in Grafana Enterprise, published on 20 Oct 2026. 

### Official description

A service account with user-management permissions in one organization can read, modify, disable or delete users belonging to other organizations on the same Grafana instance through the SCIM API (insecure direct object reference). Only Grafana Enterprise instances with SCIM enabled are affected.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-1220 (Insufficient Granularity of Access Control)

## Which versions are affected by CVE-2026-92539?

1 open source package ship an affected version, including grafana.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 11.6.0 | 12.4.13, 13.0.11, 13.1.8, 13.2.4 |

## How do I fix CVE-2026-92539?

Upgrade grafana to a fixed version for your release line: 12.4.13, 13.0.11, 13.1.8 or 13.2.4.

## Is CVE-2026-92539 being exploited?

There is no known exploitation of CVE-2026-92539 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92539 and fix it if it is affected.

What it is: CVE-2026-92539 is a medium-severity vulnerability in Grafana Enterprise, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92539 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 11.6.0; fixed in 12.4.13, 13.0.11, 13.1.8, 13.2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92539/ (Markdown: https://insights.sbomify.com/CVE-2026-92539/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92539
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92539
- OSV: https://osv.dev/vulnerability/CVE-2026-92539

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92539/
Summaries are generated and may contain mistakes; the official description above is the record.