Privilege escalation via organization-scoped API key cache
Published Apr 12, 2022 · Updated Jan 28, 2026
Privilege escalation in Grafana Enterprise 8.1.0-beta1 through 8.4.5 allows remote authenticated users to inherit another API key's permissions. The fine-grained access control permission cache builds its cache identifier at organization scope, so different API keys reuse one 30-second entry. Exploitation requires the beta feature and at least two differently privileged API keys in one organization; a lower-role key can receive prior higher-role permissions.
Summary
What happened
Privilege escalation in Grafana Enterprise 8.1.0-beta1 through 8.4.5 allows remote authenticated users to inherit another API key's permissions. The fine-grained access control permission cache builds its cache identifier at organization scope, so different API keys reuse one 30-second entry. Exploitation requires the beta feature and at least two differently privileged API keys in one organization; a lower-role key can receive prior higher-role permissions.
The record
- CVE
- CVE-2022-24812
- Published
- Apr 12, 2022
- Updated
- Jan 28, 2026
- Vendor
- Grafana Labs
- Product
- Grafana
- Classifications
- T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 2022CVE publishedPublication date reported by the CVE source.
- Jan 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 8.1.0-beta1, < 8.4.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo