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
A visitor to a public Grafana dashboard could view that dashboard’s annotation history beyond its locked time window. The flaw does not expose annotations that were otherwise invisible on the public dashboard, but it can reveal older operational context that owners expected the time restriction to hide.
Executive priority
Treat as a moderate confidentiality issue. Address promptly where public dashboards contain sensitive historical annotations; otherwise include it in normal patching. It does not warrant emergency response based on the supplied evidence.
Technical view
This is a CWE-863 authorization-control bypass affecting annotation time-range enforcement on public dashboards. It is network-accessible, requires no privileges or user interaction, and affects confidentiality only. CVSS 3.1 is 5.3. The supplied version entries do not establish clear affected or fixed ranges.
Likely exposure
Exposure is limited to Grafana or Grafana Enterprise deployments with public dashboards, annotations enabled, and locked time ranges. Risk depends on whether historical annotations contain sensitive operational details. Private dashboards and public dashboards without annotations are not identified as affected by the supplied description.
Exploitation context
The issue can be reached remotely without authentication or user interaction. The source bundle does not report CISA KEV listing, active exploitation, public exploit availability, or observed attacks. No integrity or availability impact is described.
Researcher notes
The security boundary failure concerns time-range enforcement, not access to unrelated or otherwise private annotations. Assessment should focus on public-dashboard configuration and historical annotation sensitivity. Version boundaries and a specific fixed release are not clear in the supplied data, so vendor confirmation is necessary.
Mitigation direction
Consult Grafana’s advisory and apply its supported fixed release or mitigation for your deployment.
Consider disabling annotations on affected public dashboards until remediation is confirmed.
Remove public access where historical annotations contain sensitive operational information.
Review exposed annotation history and remove sensitive details that should not remain publicly visible.
Validation and detection
Inventory public Grafana dashboards with annotations enabled and locked time ranges.
Confirm deployed versions and affected status against Grafana’s current advisory.
Review annotation history outside locked ranges for information previously assumed hidden.
After remediation, verify public views remain limited to the dashboard’s locked annotation time range.
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.