# CVE-2026-8595: Stored XSS in the table panel (TableNG)

> An Editor can inject malicious scripts into TableNG panel field names, executing code in viewers' browsers to potentially hijack accounts.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jul 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-grafana-2026-8595, GHSA-hhhx-wxgr-pj4r, MINI-522w-39qg-7ffp, MINI-5886-fx87-g749, MINI-7mfc-89qj-w472, MINI-9fvw-9j7x-xpph

## What is CVE-2026-8595?

CVE-2026-8595 is a medium-severity cross-site scripting vulnerability in Grafana Grafana, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A user with Editor permissions can craft a dashboard whose table (TableNG) panel contains a malicious field name that executes as a script in the browser of any user who views the dashboard (stored cross-site scripting).

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 12.4.0 | 12.4.4, 13.0.2 |

Products: Grafana Grafana.

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

Upgrade grafana to a fixed version for your release line: 12.4.4 or 13.0.2.

## Is CVE-2026-8595 being exploited?

There is no known exploitation of CVE-2026-8595 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-8595 and fix it if it is affected.

What it is: CVE-2026-8595 is a medium-severity cross-site scripting vulnerability in Grafana Grafana, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-8595 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 12.4.0; fixed in 12.4.4, 13.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-2026-8595/ (Markdown: https://insights.sbomify.com/CVE-2026-8595/index.md)
```

## Sources

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

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