CyberSecBulletin
CVE-2026-17183NVD status: Awaiting Analysis

Grafana OSS: Incorrect Authorization

CVE-2026-17183 is a high-severity incorrect authorization vulnerability in Grafana OSS from Grafana, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 12.3.11, 12.4.9, 13.0.7 as the first without the flaw, so updating Grafana OSS to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.29% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Grafana OSS to 12.3.11 or 12.4.9 or 13.0.7 or 13.1.4, whichever matches your release line, or a later version.
  2. Update Grafana Enterprise to 12.3.11 or 12.4.9 or 13.0.7 or 13.1.4, whichever matches your release line, or a later version.
  3. Read the advisory on grafana.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
GrafanaGrafana OSS8.4.0 up to, but not including, 12.3.11; 12.4.0 up to, but not including, 12.4.9; 13.0.0 up to, but not including, 13.0.7; 13.1.0 up to, but not including, 13.1.412.3.11, 12.4.9, 13.0.7, 13.1.4
GrafanaGrafana Enterprise8.4.0 up to, but not including, 12.3.11; 12.4.0 up to, but not including, 12.4.9; 13.0.0 up to, but not including, 13.0.7; 13.1.0 up to, but not including, 13.1.412.3.11, 12.4.9, 13.0.7, 13.1.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
LowLimited modification of data is possible.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N. Scored by CNA (grafana.com).

Official description

An authenticated user with permission to create or edit alert rules can bypass datasource query authorization by marking an alert rule query as a server-side expression while referencing a real datasource UID (incorrect authorization). This can expose data accessible through Grafana's configured datasource credentials to users who lack permission to query that datasource.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Grafana OSS

All Grafana OSS vulnerabilities

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.