# CVE-2025-6197: Open redirect in Grafana

> Attackers can redirect users to malicious sites via organization switching, requiring multiple organizations and specific user context.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Jul 2025
- **Updated:** 18 Jul 2025
- **Also known as:** BIT-grafana-2025-6197, GHSA-jvcj-qc86-j594, MINI-2822-xjpq-fq4m, MINI-5rq7-x78g-4qqq, MINI-v6px-hwqc-j5rm, MINI-x2rc-mr9j-9226, UBUNTU-CVE-2025-6197

## What is CVE-2025-6197?

CVE-2025-6197 is a medium-severity vulnerability in Grafana, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An open redirect vulnerability has been identified in Grafana OSS organization switching functionality.

Prerequisites for exploitation:

- Multiple organizations must exist in the Grafana instance

- Victim must be on a different organization than the one specified in the URL

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-6197?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 11.3.0 | 11.6.3, 12.0.2 |

## How do I fix CVE-2025-6197?

Upgrade grafana to a fixed version for your release line: 11.6.3 or 12.0.2.

## Is CVE-2025-6197 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6197 exists.

Public exploit code:

- Open Redirect via Organization Switching (nuclei): http/cves/2025/CVE-2025-6197.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6197 and fix it if it is affected.

What it is: CVE-2025-6197 is a medium-severity vulnerability in Grafana, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6197 exists.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 11.3.0; fixed in 11.6.3, 12.0.2

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

## Sources

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

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