CVE-2026-21722: Public Dashboards time range restriction on annotations can be bypassed
Public dashboards with annotations enabled did not limit their annotation timerange to the locked timerange of the public dashboard. This means one could read the entire history of annotations visible on the specific dashboard, even those outside the locked timerange.
This did not leak any annotations that would not otherwise be visible on the public dashboard.
Security readout for executives and security teams
Plain-English summary
This Grafana issue lets an unauthenticated viewer of a public dashboard read annotation history outside the dashboard’s locked time range. The source says it does not expose annotations that were not otherwise visible on that public dashboard, so the impact is limited disclosure, not system compromise.
Executive priority
Handle through normal vulnerability management with visibility-focused urgency. Prioritize internet-facing public dashboards that may contain sensitive annotations, but do not treat this as remote code execution or broad data compromise based on current evidence.
Technical view
Public dashboards with annotations enabled failed to constrain annotation queries to the dashboard’s locked time range. The CVE maps this to CWE-863 with CVSS 5.3, network-accessible, low complexity, no privileges, no user interaction, and low confidentiality impact only.
Likely exposure
Exposure is limited to Grafana public dashboards with annotations enabled. The bundle lists Grafana OSS and Grafana Enterprise versions including 9.3.0, 12.0.0, 12.2.0, and 12.3.0, but does not provide complete version-range or fix details.
Exploitation context
No active exploitation is supported by the provided sources, and the CVE is not listed as KEV. The scenario is unauthenticated remote access to public dashboard annotation history beyond the intended time window.
Researcher notes
The key boundary failure is time-range authorization for annotations on public dashboards. The source explicitly limits impact: annotations outside the locked range could be read, but only if otherwise visible on that specific public dashboard. Patch details are not present in the supplied bundle.
Mitigation direction
Review Grafana’s advisory for affected-version and upgrade guidance.
Inventory public dashboards with annotations enabled.
Treat public dashboard annotation history as potentially visible.
Reduce public dashboard or annotation exposure where business need is low.
Validation and detection
Identify Grafana OSS and Enterprise deployments using listed affected versions.
List public dashboards that have annotations enabled.
Review annotation history for sensitive operational or incident context.
Confirm vendor guidance before declaring remediation complete.
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-863: 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-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.