NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Grafana plugin data sources vulnerable to access control bypassGHSA-hh8p-374f-qgr5

MEDIUMFix: grafana/grafana@4cb3ba5

GHSA-hh8p-374f-qgr5 is a medium-severity (CVSS 4.4) CWE-266 vulnerability in github.com/grafana/grafana. A fix is available for github.com/grafana/grafana — see the affected versions and patch details below.

Also known asBIT-grafana-2024-6322CVE-2024-6322GO-2024-3079
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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 GHSA-hh8p-374f-qgr5.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk
0.00%0.27%0.54%0.80%0.0%0.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐹github.com/grafana/grafana🐹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

Access control for plugin data sources protected by the ReqActions json field of the plugin.json is bypassed if the user or service account is granted associated access to any other data source, as the ReqActions check was not scoped to each specific datasource. The account must have prior query access to the impacted datasource.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafana≥ 11.1.0&&< 11.1.111.1.1go get github.com/grafana/grafana@v11.1.1
🐹Gogithub.com/grafana/grafana≥ 11.1.2&&< 11.1.311.1.3go get github.com/grafana/grafana@v11.1.3
🐹Gogithub.com/grafana/grafana≥ 0.0.0-20240521130516-0072e4a92d89&&< 0.0.0-20240725142242-c326d865c58b0.0.0-20240725142242-c326d865c58bgo get github.com/grafana/grafana@v0.0.0-20240725142242-c326d865c58b
🐹Gogithub.com/grafana/grafana≥ 1.9.2-0.20240521130516-0072e4a92d89&&< 1.9.2-0.20240725142242-c326d865c58b1.9.2-0.20240725142242-c326d865c58bgo get github.com/grafana/grafana@v1.9.2-0.20240725142242-c326d865c58b

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update github.com/grafana/grafana to 11.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hh8p-374f-qgr5 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Access control for plugin data sources protected by the ReqActions json field of the plugin.json is bypassed if the user or service account is granted associated access to any other data source, as the ReqActions check was not scoped to each specific datasource. The account must have prior query access to the impacted datasource.
O3 Security · Impact-Aware SCA

Is GHSA-hh8p-374f-qgr5 in your dependencies?

Find it across Go, including transitive dependencies.

Grafana plugin data sources vulnerable to access control…