CVE-2026-21721VulnerabilityPublished 2 Mar 2026Updated 8 Oct 2026

SUSE · security update for grafana

Affects SUSESource GCVE Database

Authoritative record:CVE-2026-21721· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade SUSE to 12.3.1 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 12.3.1, 12.2.3, 12.1.5 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Grafanagrafana/grafana	Affected >=12.3.0 <12.3.1	Fixed in 12.3.1
Grafanagrafana/grafana	Affected >=12.2.0 <12.2.3	Fixed in 12.2.3
Grafanagrafana/grafana	Affected >=12.1.0 <12.1.5	Fixed in 12.1.5
Grafanagrafana/grafana	Affected >=12.0.0 <12.0.8	Fixed in 12.0.8
Grafanagrafana/grafana	Affected >=10.2.0 <11.6.9	Fixed in 11.6.9
Grafanagrafana/grafana-enterprise	Affected >=10.2.0 <11.6.9	Fixed in 11.6.9
Grafanagrafana/grafana-enterprise	Affected >=12.0.0 <12.0.8	Fixed in 12.0.8
Grafanagrafana/grafana-enterprise	Affected >=12.1.0 <12.1.5	Fixed in 12.1.5
Grafanagrafana/grafana-enterprise	Affected >=12.2.0 <12.2.3	Fixed in 12.2.3
Grafanagrafana/grafana-enterprise	Affected >=12.3.0 <12.3.1	Fixed in 12.3.1
GitHubgrafana/grafana`pkg:github/grafana/grafana`Other threats	Affected =12.3.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official security update fixing this vulnerability is available from Red Hat for Grafana packages in Red Hat Enterprise Linux 10.0 Extended Update Support and related variants. Users should apply the provided update (e.g., grafana-10.2.6-20.el10_0) to remediate the issue. No alternative mitigations meeting Red Hat's criteria are currently available. Organizations should prioritize patching affected systems to prevent privilege escalation.

Description

The dashboard permissions API does not verify the target dashboard scope and only checks the dashboards.permissions:* action. As a result, a user who has permission management rights on one dashboard can read and modify permissions on other dashboards. This is an organization‑internal privilege escalation.

Impact

An attacker with permission management rights on a single dashboard can read and modify permissions on other dashboards within the same organization, leading to internal privilege escalation. This compromises confidentiality and integrity of dashboard permissions but does not affect availability. The vulnerability enables unauthorized access and modification of dashboard permissions beyond the attacker's original scope.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Architecture and Design
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.
Architecture and Design
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 18:00 UTC

WeaknessesCWE-863, CWE-639

Technical details

References

Community reviews

Related threats