# CVE-2026-14199: Session takeover via Auth Proxy cache key collision

> Authenticated users can hijack sessions of higher-privileged users via cache key collisions in Grafana's Auth Proxy when identity caching is enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** BIT-grafana-2026-14199, CLSA-2026-1790248981, GHSA-9758-8g25-vw94, MINI-2p2f-jw88-224x, MINI-2p2r-6xq2-3hh2, MINI-3vhf-937g-vfpj, MINI-45p6-rpp8-gg9j, MINI-4crh-mp6j-wmmx, MINI-4xr2-vrh4-h8qr, MINI-5598-fq6j-vfwp, MINI-cjpq-hh5j-r3qm, MINI-fc3f-pfmf-fwx2, MINI-g37v-8c8v-93vq, MINI-hwqw-77mw-97f8, MINI-jcjc-8q55-wjpr, MINI-m524-vh9m-9f6j, MINI-mq5m-4xw4-2g3h, MINI-mq9c-29vp-83x4, MINI-mw9p-cr9q-f2c9, MINI-pc8r-369f-2mjr, MINI-pg8m-vcmw-rgcq, MINI-pxgq-vw63-8xjw, MINI-qpgr-j3mp-7wjc

## What is CVE-2026-14199?

CVE-2026-14199 is a high-severity authentication bypass vulnerability in Grafana Grafana, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Only self-managed Grafana instances with Auth Proxy authentication and identity caching enabled (sync_ttl greater than zero) are affected. The Auth Proxy cache key concatenated the username and forwarded identity attributes without a delimiter, so distinct identities could collide on one key. An authenticated user who shapes their own attributes to collide with a higher-privileged user's, while that user's cache entry is live, is authenticated as that user, up to Administrator (authentication bypass by spoofing).

Weakness: CWE-863 (Incorrect Authorization), CWE-290 (Authentication Bypass by Spoofing), CWE-1023 (Incomplete Comparison with Missing Factors)

## Which versions are affected by CVE-2026-14199?

1 open source package ship an affected version, including grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 11.0.0 | 12.4.10, 13.0.8, 13.2.1 |

Products: Grafana Grafana.

## How do I fix CVE-2026-14199?

Upgrade grafana to a fixed version for your release line: 12.4.10, 13.0.8 or 13.2.1.

## Is CVE-2026-14199 being exploited?

There is no known exploitation of CVE-2026-14199 in the wild and no public exploit code.

## Other vulnerabilities in Grafana Grafana

- [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild)
- [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0)
- [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8)
- [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14199 and fix it if it is affected.

What it is: CVE-2026-14199 is a high-severity authentication bypass vulnerability in Grafana Grafana, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14199 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 11.0.0; fixed in 12.4.10, 13.0.8, 13.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14199/ (Markdown: https://insights.sbomify.com/CVE-2026-14199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14199
- OSV: https://osv.dev/vulnerability/CVE-2026-14199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14199/
Summaries are generated and may contain mistakes; the official description above is the record.