# CVE-2025-41117: XSS in Grafana Explore stack trace

> Attackers can inject malicious JavaScript via stack traces in Grafana Explore when using Jaeger HTTP datasources, potentially compromising user sessions.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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:** 12 Feb 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-grafana-2025-41117, GHSA-cqp7-wf4c-3xgc, GO-2026-5332, MINI-jjq4-8gvq-x7x2, MINI-mmcc-h9qq-8ww9, MINI-v7mv-6q7g-j3mq, MINI-vcr9-rf2w-7mfh, UBUNTU-CVE-2025-41117

## What is CVE-2025-41117?

CVE-2025-41117 is a medium-severity cross-site scripting vulnerability in Grafana Grafana, published on 12 Feb 2026. 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

Stack traces in Grafana's Explore Traces view can be rendered as raw HTML, and thus inject malicious JavaScript in the browser. This would require malicious JavaScript to be entered into the stack trace field.

Only datasources with the Jaeger HTTP API appear to be affected; Jaeger gRPC and Tempo do not appear affected whatsoever.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

6 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | All versions | None |
| `github.com/grafana/grafana` | Go | From 12.2.0 | 12.2.5 |
| `github.com/grafana/grafana` | Go | From 12.2.0 | 12.2.5 |
| `github.com/grafana/grafana` | Go | From 12.3.0 | 12.3.3 |
| `github.com/grafana/grafana` | Go | From 12.3.0 | 12.3.3 |
| `grafana` | Bitnami | From 12.2.0 | 12.2.4, 12.3.2 |

Products: Grafana Grafana.

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

Upgrade github.com/grafana/grafana to a fixed version for your release line: 12.2.5 or 12.3.3.

## Is CVE-2025-41117 being exploited?

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

## Other vulnerabilities in Grafana Grafana

- [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild)
- [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0)
- [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8)
- [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41117 is a medium-severity cross-site scripting vulnerability in Grafana Grafana, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-41117 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected all versions; no fix listed
- github.com/grafana/grafana (Go): affected from 12.2.0; fixed in 12.2.5
- github.com/grafana/grafana (Go): affected from 12.2.0; fixed in 12.2.5
- github.com/grafana/grafana (Go): affected from 12.3.0; fixed in 12.3.3
- github.com/grafana/grafana (Go): affected from 12.3.0; fixed in 12.3.3
- grafana (Bitnami): affected from 12.2.0; fixed in 12.2.4, 12.3.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-41117/ (Markdown: https://insights.sbomify.com/CVE-2025-41117/index.md)
```

## Sources

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

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