How to Fix CVE-2026-21727: Incorrect permission assignment in Grafana Correlations
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 3.3 (Low) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Grafana 10.2.0 to <12.4.0 |
| Fixed in | Grafana Correlations 12.4.0 |
| Type (CWE) | CWE-732: Incorrect Permission Assignment for Critical Resource |
What is CVE-2026-21727?
--- title: Cross-Tenant Legacy Correlation Disclosure and Deletion draft: false hero: image: /static/img/heros/hero-legal2.svg content: "# Cross-Tenant Legacy Correlation Disclosure and Deletion" date: 2026-01-29 product: Grafana severity: Low cve: CVE-2026-21727 cvss_score: "3.3" cvss_vector: "CVSS:3.3/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N" fixed_versions: - ">=11.6.11 >=12.0.9 >=12.1.6 >=12.2.4" --- A cross-tenant isolation vulnerability was found in Grafana’s Correlations feature affecting legacy correlation records. Due to a backward compatibility condition allowing org_id = 0 records to be returned across organizations, a user with datasource management privileges could read and permanently delete legacy correlation data belonging to another organization. This issue affects correlations created prior to Grafana 10.2 and is fixed in >=11.6.11, >=12.0.9, >=12.1.6, and >=12.2.4. Thanks to Gyu-hyeok Lee (g2h) for reporting this vulnerability.
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s grafana 2>/dev/null | grep -i version
rpm -q grafana 2>/dev/null
grafana --version 2>/dev/null
Compare what you see against the Affected row above (Grafana 10.2.0 to <12.4.0). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-21727
The primary fix is to upgrade Grafana Correlations to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: Grafana Correlations 12.4.0.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade grafana
grafana --version 2>/dev/null || dpkg -s grafana | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security grafana -y
rpm -q grafana
SUSE / openSUSE
sudo zypper patch --category security
rpm -q grafana
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-21727 affecting Grafana Correlations
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-21727-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detecting installed version of Grafana Correlations"
$pkg = winget list --id "Grafana_Correlations" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\Grafana_Correlations-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\Grafana_Correlations" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to Grafana Correlations 12.4.0"
winget upgrade --id "Grafana_Correlations" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "Grafana_Correlations"
Write-Host "Fix applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-21727 affecting Grafana Correlations
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-21727-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s grafana 2>/dev/null | grep -i version || echo "grafana not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q grafana || echo "grafana not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-21727-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/grafana /etc/grafana.d /etc/grafana.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: Grafana Correlations 12.4.0)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y grafana
elif command -v dnf >/dev/null; then
dnf upgrade --security -y grafana
elif command -v yum >/dev/null; then
yum update -y grafana
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s grafana 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q grafana
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network restriction (Linux, nftables)
# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop grafana
sudo systemctl disable grafana
How to verify the fix worked
# Linux
grafana --version 2>/dev/null || dpkg -s grafana | grep -i version
rpm -q grafana 2>/dev/null || true
# Windows
winget list | findstr /I "grafana"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above Grafana Correlations 12.4.0. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-6036: SQL injection in Vehicle Showroom Management System — SQL injection in Vehicle Showroom Management System
- How to Fix CVE-2026-7229: SQL Injection in Coaching Management System — SQL Injection in Coaching Management System
- How to Fix CVE-2026-39459: Critical Vulnerability in BIG-IP , Critical Vulnerability in BIG-IP
- How to Fix CVE-2026-28551: Cwe-362 concurrent execution using shared resource with improper synchronization. , Cwe-362 concurrent execution using shared resource with improper synchronization.
- How to Fix CVE-2026-24851: Access Control Bypass in openfga , Access Control Bypass in openfga
Is CVE-2026-21727 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
3.3 (low). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://grafana.com/security/security-advisories/cve-2026-21727
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21727
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*