# Grafana Race condition allowing privilege escalation

Advisory record · `GHSA-vqc4-mpj8-jxch`

- **Identifiers:** `GHSA-vqc4-mpj8-jxch` · `BIT-grafana-2022-39328` · `CVE-2022-39328` · `GO-2024-2856`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-362](https://cwe.mitre.org/data/definitions/362.html)
- **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md)
- **Published:** 14 May 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2024, 22:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/grafana/grafana` (Go): affected `>=9.2.0, <9.2.4`; fixed in `9.2.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Grafana (github.com/grafana/grafana) versions 9.2.0 up to but not including 9.2.4 are affected by a race condition in HTTP context creation that can assign a request the authentication and authorization middleware of a different call. An unauthenticated attacker can exploit this under heavy load to query protected endpoints. Upgrade to Grafana 9.2.4 to fix the issue.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.013, the 71st percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vqc4-mpj8-jxch)

## Sources

- [GitHub Advisory Database: GHSA-vqc4-mpj8-jxch](https://github.com/advisories/GHSA-vqc4-mpj8-jxch)
- [OSV: GHSA-vqc4-mpj8-jxch](https://osv.dev/vulnerability/GHSA-vqc4-mpj8-jxch)
- <https://github.com/grafana/grafana/security/advisories/GHSA-vqc4-mpj8-jxch>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-39328>
- <https://github.com/grafana/grafana>
- <https://security.netapp.com/advisory/ntap-20221215-0003>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vqc4-mpj8-jxch>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vqc4-mpj8-jxch/>. Everything for agents: <https://agentprime.io/llms.txt>.
