# CVE-2026-19197: Broken access control in dashboard snapshots

> Organization admins can delete other orgs' snapshots and recover secret keys, allowing unauthorized data modification and disclosure.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-grafana-2026-19197, GHSA-ccq3-xjc6-g2c3, MINI-9g4h-9f6h-vj6v, MINI-qf2x-5qcx-cf37, MINI-r9xf-8vw3-hfxr, MINI-v864-6g78-p5j9, MINI-vp65-54pm-9m83, MINI-vx36-4qfx-g3x4, UBUNTU-CVE-2026-19197

## What is CVE-2026-19197?

CVE-2026-19197 is a medium-severity missing authorization vulnerability in Grafana Enterprise, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A user with organization administrator permissions can delete dashboard snapshots belonging to other organizations on the same Grafana instance, and can recover a snapshot's secret delete key using only its public share key (broken access control).

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 12.4.0 | 12.4.8, 13.0.6, 13.1.3 |

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

Upgrade grafana to a fixed version for your release line: 12.4.8, 13.0.6 or 13.1.3.

## Is CVE-2026-19197 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19197 is a medium-severity missing authorization vulnerability in Grafana Enterprise, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19197 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 12.4.0; fixed in 12.4.8, 13.0.6, 13.1.3

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-19197/ (Markdown: https://insights.sbomify.com/CVE-2026-19197/index.md)
```

## Sources

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

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