When independent Grafana instances share the same [rendering] renderer_token, an image renderer key issued by one
Source GCVE Database
Not known to be exploited · CVSS 7.1 High.
Data as of 11 Nov 2026, 16:20 UTC
Thin evidence
One scorer or none| CNA (GRAFANA) | CVSS 3.1 | 7.1 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GrafanaGrafana OSS | Affected
| Fixed in– |
| GrafanaGrafana Enterprise | Affected
| Fixed in– |
AI-suggested
Since the vulnerability depends on sharing the same renderer_token across independent instances and the renderAuthJWT feature toggle being enabled, administrators should ensure that each Grafana instance uses a unique renderer_token and review the configuration of the renderAuthJWT feature toggle.
Description
This vulnerability affects independent Grafana instances that share the same rendering renderer_token. When the renderAuthJWT feature toggle is enabled (default from Grafana 13.0.0), an image renderer key issued by one instance is accepted by others sharing the token. This allows a user on one instance to impersonate a user with the same ID on another instance due to origin validation errors.