CVE
Cross-instance user impersonation through image renderer JWTs
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Grafana OSS and Grafana Enterprise instances that share the same image renderer token accept each other's renderer keys, so a remote attacker with a low-privilege login on one instance can act as the user with the same ID on another. The flaw affects instances with the renderAuthJWT feature toggle enabled, which is on by default.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
When independent Grafana instances share the same [rendering] renderer_token, an image renderer key issued by one instance is accepted by the others, so a user on one instance could act as the user with the same ID on another (origin validation error). This affects instances with the renderAuthJWT feature toggle enabled, the default from Grafana 13.0.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-102589 (Cross-instance user impersonation through image renderer JWTs), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-102589 (entry last updated 2026-11-11):
Affected:
- Grafana Grafana OSS: from 9.5.0, through 12.3.11; from 12.4.0, through 12.4.14; from 13.0.0, through 13.0.12; from 13.1.0, through 13.1.9; from 13.2.0, through 13.2.5; version 13.3.0
- Grafana Grafana Enterprise: from 9.5.0, through 12.3.11; from 12.4.0, through 12.4.14; from 13.0.0, through 13.0.12; from 13.1.0, through 13.1.9; from 13.2.0, through 13.2.5; version 13.3.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-102589 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102589 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://grafana.com/security/security-advisories/cve-2026-102589
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-102589
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-102589"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Grafana Grafana OSS
From 9.5.0 · through 12.3.11; From 12.4.0 · through 12.4.14; From 13.0.0 · through 13.0.12; From 13.1.0 · through 13.1.9; From 13.2.0 · through 13.2.5; From 13.3.0 · through 13.3.0
- Grafana Grafana Enterprise
From 9.5.0 · through 12.3.11; From 12.4.0 · through 12.4.14; From 13.0.0 · through 13.0.12; From 13.1.0 · through 13.1.9; From 13.2.0 · through 13.2.5; From 13.3.0 · through 13.3.0
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-102589
Is CVE-2026-102589 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-102589?
Grafana OSS: from 9.5.0 through 12.3.11; from 12.4.0 through 12.4.14; from 13.0.0 through 13.0.12; from 13.1.0 through 13.1.9; from 13.2.0 through 13.2.5; from 13.3.0 through 13.3.0. Grafana Enterprise: from 9.5.0 through 12.3.11; from 12.4.0 through 12.4.14; from 13.0.0 through 13.0.12; from 13.1.0 through 13.1.9; from 13.2.0 through 13.2.5; from 13.3.0 through 13.3.0.Source: cve.now feed data