# CVE-2026-10601: Path traversal in the Tempo and Loki data source plugins > A Viewer can exploit path traversal in Tempo and Loki plugins to access backend endpoints, potentially leaking credentials or triggering administrative actions. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 22 Jun 2026 - **Updated:** 27 Aug 2026 - **Also known as:** BIT-grafana-2026-10601, GHSA-9493-h4f5-633x, GO-2026-6545, MINI-2fc2-27hq-x36f, MINI-3p3v-pg5c-mgjg, MINI-4jgq-22g7-879f, MINI-6g4h-p7f3-84pf, MINI-6vww-cf9m-vj48, MINI-7fhx-mfq2-x86c, MINI-9779-j6c4-6f3f, MINI-f4q5-ffqr-prmg, MINI-fxxg-pcxm-546c, MINI-gpvg-rp9w-g3c8, MINI-gq97-p7qv-j799, MINI-h83g-hj3v-xm65, MINI-hgq6-g4jq-pmjv, MINI-jj8c-5hmj-q9v3, MINI-r36w-6q53-cg33, MINI-w3v4-756r-gw7j, MINI-wp5m-pqw9-h6cm, MINI-xvxf-38m9-x8vf, RHSA-2026:64525, RHSA-2026:64585 ## What is CVE-2026-10601? CVE-2026-10601 is a medium-severity path traversal vulnerability in Grafana Grafana, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A user with Viewer permissions can use specially crafted requests to the Tempo and Loki data source plugins to reach unintended backend endpoints. Depending on the backend configuration this can expose data source credentials, leak internal responses, or trigger administrative actions on the configured backend. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-10601? 15 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 | All versions | 1.9.2-0.20260616075434-82ef13993059 | | `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260616075434-82ef13993059 | | `github.com/grafana/grafana` | Go | From 12.0.0 | None | | `github.com/grafana/grafana` | Go | From 12.0.0 | None | | `github.com/grafana/grafana` | Go | From 12.3.0 | None | | `github.com/grafana/grafana` | Go | From 12.3.0 | None | | `github.com/grafana/grafana` | Go | From 12.4.0 | None | | `github.com/grafana/grafana` | Go | From 12.4.0 | None | | `github.com/grafana/grafana` | Go | From 13.0.0 | None | | `github.com/grafana/grafana` | Go | From 13.0.0 | None | | `github.com/grafana/grafana` | Go | From 2.0.0-beta1 | None | | `github.com/grafana/grafana` | Go | From 2.0.0-beta1 | None | | `github.com/grafana/grafana` | Go | From 2.0.0-beta1+incompatible | None | | `grafana` | Bitnami | All versions | 11.6.15, 12.2.9, 12.3.7, 12.4.4, 13.0.2 | | `loki3.6` | Red Hat:hummingbird:1 | All versions | 0:3.6.16-0.1.hum1 | | `loki3.6-canary` | Red Hat:hummingbird:1 | All versions | 0:3.6.16-0.1.hum1 | | `loki3.6-logcli` | Red Hat:hummingbird:1 | All versions | 0:3.6.16-0.1.hum1 | | `loki3.7` | Red Hat:hummingbird:1 | All versions | 0:3.7.7-0.1.hum1 | | `loki3.7-canary` | Red Hat:hummingbird:1 | All versions | 0:3.7.7-0.1.hum1 | | `loki3.7-logcli` | Red Hat:hummingbird:1 | All versions | 0:3.7.7-0.1.hum1 | Products: Grafana Grafana. ## How do I fix CVE-2026-10601? Upgrade github.com/grafana/grafana to 1.9.2-0.20260616075434-82ef13993059 or later. ## Is CVE-2026-10601 being exploited? There is no known exploitation of CVE-2026-10601 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-2026-10601 and fix it if it is affected. What it is: CVE-2026-10601 is a medium-severity path traversal vulnerability in Grafana Grafana, published on 22 Jun 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-10601 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 all versions; fixed in 1.9.2-0.20260616075434-82ef13993059 - github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260616075434-82ef13993059 - github.com/grafana/grafana (Go): affected from 12.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.3.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.3.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.4.0; no fix listed - github.com/grafana/grafana (Go): affected from 12.4.0; no fix listed - github.com/grafana/grafana (Go): affected from 13.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 13.0.0; no fix listed - github.com/grafana/grafana (Go): affected from 2.0.0-beta1; no fix listed 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-10601/ (Markdown: https://insights.sbomify.com/CVE-2026-10601/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10601 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10601 - OSV: https://osv.dev/vulnerability/CVE-2026-10601 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-10601/ Summaries are generated and may contain mistakes; the official description above is the record.