Grafana: Improper Control of Generation of Code
CVE-2026-27876 is a critical-severity improper control of generation of code vulnerability in Grafana, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 11.6.14, 12.1.10, 12.2.8 as the first without the flaw, so updating Grafana to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.01% chance of exploitation within 30 days, higher than 81% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Grafana to 11.6.14 or 12.1.10 or 12.2.8 or 12.3.6, whichever matches your release line, or a later version.
- Read the advisory on grafana.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Grafana | Grafana | 11.6.0 up to, but not including, 11.6.14; 12.0.0 up to, but not including, 12.1.10; 12.2.0 up to, but not including, 12.2.8; 12.3.0 up to, but not including, 12.3.6; 12.4.0 up to, but not including, 12.4.2 | 11.6.14, 12.1.10, 12.2.8, 12.3.6, 12.4.2 |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
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
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (grafana.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | CNA (grafana.com) |
| CVSS 3.1 | 9.1 | Critical | CNA |
Official description
A chained attack via SQL Expressions and a Grafana Enterprise plugin can lead to a remote arbitrary code execution impact (RCE). This is enabled by a feature in Grafana (OSS), so all users are always recommended to update to avoid future attack vectors going this path. Only instances with the sqlExpressions feature toggle enabled are vulnerable. Only instances in the following version ranges are affected: - 11.6.0 (inclusive) to 11.6.14 (exclusive): 11.6.14 has the fix. 11.5 and below are not affected. - 12.0.0 (inclusive) to 12.1.10 (exclusive): 12.1.10 has the fix. 12.0 did not receive an update, as it is end-of-life. - 12.2.0 (inclusive) to 12.2.8 (exclusive): 12.2.8 has the fix. - 12.3.0 (inclusive) to 12.3.6 (exclusive): 12.3.6 has the fix. - 12.4.0 (inclusive) to 12.4.2 (exclusive): 12.4.2 has the fix. 13.0.0 and above also have the fix: no v13 release is affected.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Grafana
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.1 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 8.1 High severity
- 9.8 Critical severity
- 7.2 High severity
- 9.9 Critical severity
Spotted an error? Tell us.