dbcve.org
GrafanaApplication

CVE-2026-8595

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 12.4.4 / 13.0.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored cross-site scripting vulnerability in the TableNG panel component allows users with Editor permissions to inject malicious JavaScript through crafted field names. When other users view the dashboard, the script executes in their browser context.

MitigationImplement strict input validation and output encoding for field names in TableNG panels; consider Content Security Policy headers as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 12.4.0, < 12.4.4>= 13.0.0, < 13.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana version
    Query the Grafana API endpoint /api/health or run grafana-server --version from the command line to retrieve the installed version number
    Affected if The installed version falls within 12.4.0 to <12.4.4 or 13.0.0 to <13.0.2
  2. Locate TableNG panels in dashboards
    Use the Grafana HTTP API (e.g., GET /api/search?type=dash-db) to list all dashboards, then inspect each dashboard JSON model for panels with type 'tableNG' or search database tables (dashboard and panel_options) for TableNG panel instances
    Affected if Any dashboard contains a panel with type 'tableNG' and the Grafana version is within the affected ranges
  3. Check for Editor role users
    Query the Grafana user API (GET /api/users) or inspect the user authentication database to identify accounts assigned the Editor role
    Affected if Any user with Editor permissions exists in the system and TableNG panels are present
  4. Verify TableNG feature availability
    Check Grafana feature toggle configuration via /api/frontend/settings or configuration files for 'tableNG' or 'newPanelChrome' flags, which control TableNG panel availability
    Affected if TableNG feature is enabled (explicitly or by default) and the Grafana version is affected

The environment is affected if Grafana version is 12.4.0-12.4.3 or 13.0.0-13.0.1, TableNG panels exist in any dashboard, and at least one user with Editor permissions can create or modify those panels.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.4.4 / 13.0.2 or later
Fixed in 12.4.413.0.2
Interim mitigation

Implement strict input validation and output encoding for field names in TableNG panels; consider Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

Grafana 12.4.4 or later for 12.x branch; Grafana 13.0.2 or later for 13.x branch

  1. Upgrade Grafana to version 12.4.4 or later if running version 12.x
  2. Upgrade Grafana to version 13.0.2 or later if running version 13.x
  3. After upgrading, verify the TableNG panel functionality works as expected
  4. Review dashboards that use TableNG panels for any suspicious field names

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8595 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data