Security readout for executives and security teams
Plain-English summary
CVE-2026-28374 is an access-control flaw in Grafana OSS annotations. An authenticated editor could delete annotations they should not be able to read or manage. This is primarily an integrity issue, not a data theft issue, and the published severity is medium.
Executive priority
Treat as a medium-priority integrity issue. It is unlikely to cause system takeover, but it can undermine operational records, incident timelines, or dashboard context if untrusted editors exist.
Technical view
The issue is an IDOR-style authorization failure in the Annotations API. CVSS 3.1 is 4.3: network-reachable, low complexity, low privileges required, no user interaction, low integrity impact, no confidentiality or availability impact. The listed CWE is CWE-284.
Likely exposure
Exposure is most relevant for Grafana OSS deployments running the versions listed in the CVE source bundle and allowing editor-level users. Risk depends on use of annotations and trust boundaries between editor users, dashboards, teams, or tenants.
Exploitation context
No active exploitation is stated in the provided sources, and this CVE is not marked as CISA KEV. Abuse would require an authenticated editor account and could result in unauthorized deletion of annotations.
Researcher notes
Sources identify Grafana OSS and an Annotations API IDOR allowing editors to delete annotations without read access. The bundle does not provide exploit details or explicit fixed versions, so remediation should be aligned to Grafana’s advisory.
Mitigation direction
Review Grafana’s vendor advisory for affected and fixed version guidance.
Upgrade or apply vendor-recommended remediation when confirmed for your Grafana release.
Restrict editor privileges to users with a business need.
Monitor annotation deletion activity for unexpected editor accounts.
Back up dashboards and operational annotation data where business-critical.
Validation and detection
Inventory Grafana OSS versions against the CVE’s listed affected versions.
Confirm whether editor users exist in exposed or shared environments.
Review access controls for dashboards, teams, and annotation management.
Check logs or audit sources for unusual annotation deletion events.
Track the vendor advisory for updated remediation details.
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 · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
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-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.