Grafana up to 12.4.1 Public Dashboard Deletion Endpoint improper isolation or compartmentalization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.57 |
Summary
A vulnerability identified as problematic has been detected in Grafana up to 11.6.13/12.1.9/12.2.7/12.3.5/12.4.1. Affected by this issue is some unknown functionality of the component Public Dashboard Deletion Endpoint. Performing a manipulation results in improper isolation or compartmentalization. This vulnerability is reported as CVE-2026-28378. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Grafana up to 11.6.13/12.1.9/12.2.7/12.3.5/12.4.1. This affects some unknown functionality of the component Public Dashboard Deletion Endpoint. The manipulation with an unknown input leads to a improper isolation or compartmentalization vulnerability. CWE is classifying the issue as CWE-653. The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The public dashboard deletion endpoint does not enforce organization isolation, allowing an Org Admin in one organization to delete public dashboards belonging to a different organization by supplying the target dashboard's identifiers.
It is possible to read the advisory at grafana.com. This vulnerability is uniquely identified as CVE-2026-28378 since 02/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/07/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 11.6.0
- 11.6.1
- 11.6.2
- 11.6.3
- 11.6.4
- 11.6.5
- 11.6.6
- 11.6.7
- 11.6.8
- 11.6.9
- 11.6.10
- 11.6.11
- 11.6.12
- 11.6.13
- 12.1.0
- 12.1.1
- 12.1.2
- 12.1.3
- 12.1.4
- 12.1.5
- 12.1.6
- 12.1.7
- 12.1.8
- 12.1.9
- 12.2.0
- 12.2.1
- 12.2.2
- 12.2.3
- 12.2.4
- 12.2.5
- 12.2.6
- 12.2.7
- 12.3.0
- 12.3.1
- 12.3.2
- 12.3.3
- 12.3.4
- 12.3.5
- 12.4.0
- 12.4.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper isolation or compartmentalizationCWE: CWE-653
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/27/2026 CVE reserved07/07/2026 Advisory disclosed
07/07/2026 VulDB entry created
07/07/2026 VulDB entry last update
Sources
Advisory: grafana.comStatus: Confirmed
CVE: CVE-2026-28378 (🔒)
GCVE (CVE): GCVE-0-2026-28378
GCVE (VulDB): GCVE-100-376707
Entry
Created: 07/07/2026 23:59Changes: 07/07/2026 23:59 (51)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.