Bug 2565151 (CVE-2026-102589)

Summary: CVE-2026-102589 grafana: IMAGE RENDER KEYS COULD BE REPLAYED ACROSS GRAFANA INSTANCES THAT SHARE A RENDERER TOKEN
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: amctagga, aoconnor, bniver, flucifre, gmeno, gparvin, groman, jbalunas, lchilton, mbenjamin, mhackett, rhaigner, rhel-process-autobot, security-response-team, sfeifer, sostapov, tsze, vereddy, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Grafana. In environments where independent Grafana deployments share the same image renderer token, render keys are not restricted to the issuing instance. An authenticated remote attacker can replay a valid render key against another instance that shares the token, allowing them to impersonate a different user. This flaw enables privilege escalation and unauthorized access to sensitive dashboards and resources.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2026-11-10   

Description OSIDB Bzimport 2026-11-02 12:42:07 UTC
CVE-2026-102589: IMAGE RENDER KEYS COULD BE REPLAYED ACROSS GRAFANA INSTANCES THAT SHARE A RENDERER TOKEN

Score: 7.1 (HIGH) 

Short description of the vulnerability: 

When independent Grafana instances used the same renderer token, a render key issued by one instance could be accepted by another and act as a different user there. The fixed versions bind each render key to the instance that issued it. 

Known mitigations: 

Disable the renderAuthJWT feature toggle on every affected instance, or use a distinct renderer token for each independent instance. For the partner-only 11.6 backport, renderAuthJWT must be explicitly disabled before upgrading; the patched build uses cache-based render authentication. 

Affected products and versions: 

Grafana and Grafana Enterprise 12.4.0 to 12.4.14, 13.0.0 to 13.0.12, 13.1.0 to 13.1.9, 13.2.0 to 13.2.5, and 13.3.0. Versions 9.5.0 to 12.3.11 are also affected. The 11.6 line receives a partner-only fix in the 27 October 11.6.17+security-01 re-cut; other retired lines have no new fix planned in this release. This partner-only re-cut is separate from the five supported customer builds listed above. 

Affected platforms: 

Self-managed (on-premise), when independent instances share a renderer token