Skip to content
Noroxi
NVD / CVE Program· CNA GRAFANA

CVE-2026-102589: Cross-instance user impersonation through image renderer JWTs

HighCVSS 7.1 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org

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.

Published
Nov 11, 2026
Updated
Nov 11, 2026
EPSS
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

CNA vs NVD score

NVD
—
CNA · GRAFANA
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-102589

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for grafana records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GRAFANA). Independent of NVD's CPE analysis and usually ahead of it.

  • Grafana Grafana Enterprise

    • 9.5.0 and later · up to and including 12.3.11affected · semver
    • 12.4.0 and later · up to and including 12.4.14affected · semver
    • 13.0.0 and later · up to and including 13.0.12affected · semver
    • 13.1.0 and later · up to and including 13.1.9affected · semver
    • 13.2.0 and later · up to and including 13.2.5affected · semver
    • 13.3.0 and later · up to and including 13.3.0affected · semver

  • Grafana Grafana OSS

    • 9.5.0 and later · up to and including 12.3.11affected · semver
    • 12.4.0 and later · up to and including 12.4.14affected · semver
    • 13.0.0 and later · up to and including 13.0.12affected · semver
    • 13.1.0 and later · up to and including 13.1.9affected · semver
    • 13.2.0 and later · up to and including 13.2.5affected · semver
    • 13.3.0 and later · up to and including 13.3.0affected · semver

Same product

grafana: all records

Other highest-scoring records for the same primary product.

Published before and after this one in the same product

  • ← EarlierCVE-2026-88858Oct 28, 2026 · Server-side expression parser denial of service
    26Monitor
  • ← EarlierCVE-2026-79656Oct 28, 2026 · OAuth and OIDC tokens written unredacted to server logs by the Generic OAuth, Google and GitLab connectors
    24Monitor
  • Later →CVE-2026-107509Nov 11, 2026 · Memory exhaustion denial of service in SQL Expressions
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records