# CVE-2025-3454: Grafana's datasource proxy API allows authorization checks to be bypassed

> Attackers with minimal permissions can bypass authorization checks to read data from Alertmanager and Prometheus datasources via URL manipulation.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **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:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** BIT-grafana-2025-3454, GHSA-9j65-rv5x-4vrf, GO-2025-3742, MINI-2hrv-76pp-pjj4, MINI-7h3r-g4h9-wwmg, MINI-7mxg-fcwv-jgqq, MINI-8gmf-h9c7-cgg9, MINI-9242-r866-cmxq, MINI-cv82-9759-8vp2, MINI-fjmg-9m82-gc95, MINI-fmr4-hgxq-378w, MINI-fpqj-xp2x-rx85, MINI-g6fw-w834-v9rp, MINI-h8m5-j693-3h57, MINI-j5mq-xwvr-r9xx, MINI-q2qj-g54g-vch2, MINI-v8f8-gh88-8jq9, MINI-x54q-739m-pc6f, MINI-xp25-46v8-763r, MINI-xpv6-7qxh-73w8, UBUNTU-CVE-2025-3454

## What is CVE-2025-3454?

CVE-2025-3454 is a medium-severity authentication bypass vulnerability in Grafana, published on 2 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This vulnerability in Grafana's datasource proxy API allows authorization checks to be bypassed by adding an extra slash character in the URL path.

Users with minimal permissions could gain unauthorized read access to GET endpoints in Alertmanager and Prometheus datasources.

The issue primarily affects datasources that implement route-specific permissions, including Alertmanager and certain Prometheus-based datasources.

Weakness: CWE-285 (Improper Authorization)

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

4 open source packages ship an affected version, including github.com/grafana/grafana and grafana.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | From 0.0.0-20210414170620-dadccdda06e6 | None |
| `github.com/grafana/grafana` | Go | From 0.0.0-20210414170620-dadccdda06e6 | 0.0.0-20250424191517-1f707d16ed5d |
| `github.com/grafana/grafana` | Go | From 0.0.0-20210414170620-dadccdda06e6 | 0.0.0-20250424191517-1f707d16ed5d |
| `grafana` | Bitnami | From 10.4.0 | 10.4.17, 11.5.3, 11.6.0 |

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

Upgrade github.com/grafana/grafana to 0.0.0-20250424191517-1f707d16ed5d or later.

## Is CVE-2025-3454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3454 is a medium-severity authentication bypass vulnerability in Grafana, published on 2 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3454 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected from 0.0.0-20210414170620-dadccdda06e6; no fix listed
- github.com/grafana/grafana (Go): affected from 0.0.0-20210414170620-dadccdda06e6; fixed in 0.0.0-20250424191517-1f707d16ed5d
- github.com/grafana/grafana (Go): affected from 0.0.0-20210414170620-dadccdda06e6; fixed in 0.0.0-20250424191517-1f707d16ed5d
- grafana (Bitnami): affected from 10.4.0; fixed in 10.4.17, 11.5.3, 11.6.0

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

## Sources

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

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