How severe is CVE-2024-9264?

No CVSS score has been assigned to CVE-2024-9264 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-9264?

CVE-2024-9264 affects the following packages: github.com/grafana/grafana (Go), github.com/grafana/grafana (Go), github.com/grafana/grafana (Go). Ecosystems affected: Go.

How do I fix CVE-2024-9264?

Update github.com/grafana/grafana to 11.0.6+security-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9264 is resolved across your whole dependency graph.

How do I detect CVE-2024-9264 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-9264 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2024-9264 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2024-9264, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-9264?

CVE-2024-9264 has an EPSS (Exploit Prediction Scoring System) score of 97.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2024-9264?

CVE-2024-9264 is classified as Code Injection (CWE-94), CWE-77 (CWE-77). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2024-9264?

A Nuclei detection template exists for CVE-2024-9264, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-9264 published, and has it been updated?

CVE-2024-9264 was published on October 18, 2024 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2024-9264 — grafana

Fix: grafana/grafana#81666

CVE-2024-9264 is a Code Injection vulnerability in github.com/grafana/grafana. 7 public exploit references exist, so weaponization risk is real. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below.

Grafana SQL Expressions allow for remote code execution

Also known asBIT-grafana-2024-9264GHSA-q99m-qcv4-fpm7GO-2024-3215

Published

Oct 18, 2024

Updated

Oct 21, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

7 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-9264.

EPSS Exploitation Probability

via FIRST.org ↗

97.1%probability of exploitation in next 30 days

Very High Risk+2.27%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The SQL Expressions experimental feature of Grafana allows for the evaluation of duckdb queries containing user input. These queries are insufficiently sanitized before being passed to duckdb, leading to a command injection and local file inclusion vulnerability. Any user with the VIEWER or higher permission is capable of executing this attack. The duckdb binary must be present in Grafana's $PATH for this attack to function; by default, this binary is not installed in Grafana distributions.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/grafana/grafana`	≥ 11.0.0&&< 11.0.6+security-01	11.0.6+security-01`go get github.com/grafana/grafana@v11.0.6+security-01`
🐹Go	`github.com/grafana/grafana`	≥ 11.1.0&&< 11.1.7+security-01	11.1.7+security-01`go get github.com/grafana/grafana@v11.1.7+security-01`
🐹Go	`github.com/grafana/grafana`	≥ 11.2.0&&< 11.2.2+security-01	11.2.2+security-01`go get github.com/grafana/grafana@v11.2.2+security-01`

Affected Products

1 product · 1 configurations

Application

grafanagrafana

1 version

11.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The SQL Expressions experimental feature of Grafana allows for the evalu…

github.comGithubOct 2024

The SQL Expressions experimental feature of Grafana allows for the evalu…

github.comGithubOct 2024

The SQL Expressions experimental feature of Grafana allows for the evalu…

github.comGithubOct 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/grafana to 11.0.6+security-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9264 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2024-9264

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2024-9264 -u https://target

Template: Grafana Post-Auth DuckDB - SQL Injection To File Read
Severity: critical
Impact: Authenticated users with VIEWER or higher permissions can exploit SQL injection to read local files and execute commands through duckdb queries when the duckdb binary is present, potentially exposing sensitive configuration files and credentials.
Remediation: Apply the vendor-supplied patch or upgrade to a non-vulnerable version.

Template by ProjectDiscovery nuclei-templates (princechaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

This vulnerability is classified as critical instead of important because it allows for command injection and local file inclusion, potentially leading to arbitrary code execution or unauthorized access to sensitive files. The exploit can be carried out by any user with VIEWER or higher permissions, significantly…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2024-9264 (CC BY 4.0)

Frequently Asked Questions

The SQL Expressions experimental feature of Grafana allows for the evaluation of `duckdb` queries containing user input. These queries are insufficiently sanitized before being passed to `duckdb`, leading to a command injection and local file inclusion vulnerability. Any user with the VIEWER or higher permission is capable of executing this attack. The `duckdb` binary must be present in Grafana's $PATH for this attack to function; by default, this binary is not installed in Grafana distributions.