CVE-2026-21724: Missing Protected-field Authorization in Provisioning Contact Points API
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.
Security readout for executives and security teams
Plain-English summary
Grafana OSS has an authorization bypass affecting protected alert contact point settings. A user with Editor access may change protected webhook URLs without the special permission that should be required. This can redirect alert notifications or expose limited sensitive routing information.
Executive priority
Treat this as a moderate-priority access-control issue. Prioritize environments where Editors are numerous, externally managed, or less trusted, because alert webhooks can affect incident response routing and data exposure.
Technical view
The issue is CWE-285 in the provisioning contact points API. Authenticated users with the Editor role can modify protected webhook URL fields despite lacking alert.notifications.receivers.protected:write. The CVSS 3.1 score is 5.4, reflecting low-complexity, network-accessible exploitation requiring privileges, with limited confidentiality and integrity impact.
Likely exposure
Exposure is most likely in Grafana OSS instances running the listed affected versions where Editor users exist and the provisioning contact points API is reachable.
Exploitation context
The source bundle does not show KEV listing or cited evidence of active exploitation. Abuse requires authenticated Editor-level access, so insider misuse or compromised Editor accounts are the main concerns.
Researcher notes
Evidence is limited to the CVE metadata and Grafana advisory reference. The bundle identifies the authorization boundary failure but does not include exploit details, proof of active exploitation, or specific fixed versions.
Mitigation direction
Check Grafana's vendor advisory for confirmed fixed versions and remediation guidance.
Restrict Editor role assignment to users with a current business need.
Limit provisioning API access to trusted networks or administrative paths where possible.
Review protected webhook URLs for unauthorized or unexpected changes.
Rotate webhook secrets if protected URLs may have been exposed or modified.
Validation and detection
Inventory Grafana OSS instances and compare versions against 12.3.1, 12.2.2, 12.1.5, and 11.6.9.
List users and service accounts with Editor permissions.
Audit alert contact point change history for protected webhook URL modifications.
Confirm whether compensating access controls restrict provisioning contact point API reachability.
After remediation, verify protected-field changes require the documented protected-write permission.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-285 · source CWE mapping
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.