# CVE-2026-21724: Missing Protected-field Authorization in Provisioning Contact Points API

> Editors can modify protected webhook URLs in Grafana OSS without proper permissions, bypassing authorization controls.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 26 Mar 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-grafana-2026-21724, GHSA-7g92-g4vh-hp84, GO-2026-5219, MINI-2v58-35xh-63m5, MINI-3h3q-m2p8-874q, MINI-3m8r-c538-g455, MINI-7qpp-pgg8-rvx7, MINI-9jjj-xw7w-qc9x, MINI-qm9r-f56m-874m, MINI-w4mv-f233-53q2, MINI-w5wg-hw6j-5gv5, UBUNTU-CVE-2026-21724

## What is CVE-2026-21724?

CVE-2026-21724 is a medium-severity missing authorization vulnerability in Grafana Grafana, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been discovered in Grafana OSS where an authorization bypass in the provisioning contact points API allows users with Editor role to modify protected webhook URLs without the required alert.notifications.receivers.protected:write permission.

Weakness: CWE-285 (Improper Authorization)

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

4 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | All versions | None |
| `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260323180334-daffe750de85 |
| `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260323180334-daffe750de85 |
| `grafana` | Bitnami | From 11.6.9 | 11.6.14, 12.1.10, 12.2.8, 12.3.6 |

Products: Grafana Grafana.

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

Upgrade github.com/grafana/grafana to 1.9.2-0.20260323180334-daffe750de85 or later.

## Is CVE-2026-21724 being exploited?

There is no known exploitation of CVE-2026-21724 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-21724 and fix it if it is affected.

What it is: CVE-2026-21724 is a medium-severity missing authorization vulnerability in Grafana Grafana, published on 26 Mar 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-21724 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected all versions; no fix listed
- github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260323180334-daffe750de85
- github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260323180334-daffe750de85
- grafana (Bitnami): affected from 11.6.9; fixed in 11.6.14, 12.1.10, 12.2.8, 12.3.6

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-21724/ (Markdown: https://insights.sbomify.com/CVE-2026-21724/index.md)
```

## Sources

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

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