GrafanaApplication
CVE-2026-21722
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPublic 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Grafana vulnerability where public dashboards with annotations enabled fail to restrict annotation queries to the locked timerange. While annotations outside the locked timerange were visible, the timerange selector was not properly enforcing the locked range on annotation queries, allowing users to read the full history of annotations even outside the configured time boundaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GrafanaApplication
>= 9.3.0, < 11.6.10>= 12.0.0, < 12.1.6>= 12.2.0, <= 12.2.4>= 12.3.0, <= 12.3.2= 11.6.10= 12.1.6= 12.2.4= 12.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Grafana versionRun 'grafana-server --version' or check the UI at Administration > Stats. Compare the installed version against the affected ranges: >= 9.3.0, < 11.6.10; >= 12.0.0, < 12.1.6; >= 12.2.0, <= 12.2.4; >= 12.3.0, <= 12.3.2; = 11.6.10; = 12.1.6; = 12.2.4; = 12.3.2Affected if The installed version falls within any of the affected version ranges
-
Identify public dashboards with annotationsIn Grafana UI, navigate to Dashboards > Public or query the database table 'dashboard' where 'is_public' = true. For each public dashboard, check if annotations are enabled in Dashboard Settings > Annotations.Affected if There exist public dashboards with annotations enabled
-
Verify timerange lock configurationFor each public dashboard with annotations, go to Dashboard Settings > Time range and check if 'Lock time range' is enabled. Also inspect the dashboard JSON model (Dashboard Settings > JSON model) for 'timepicker' section with 'locked' property set to true.Affected if Timerange lock is enabled on a public dashboard that has annotations enabled
-
Confirm annotation query behavior outside locked rangeOn an affected public dashboard with locked timerange and annotations enabled, manually change the URL timerange parameters (e.g., ?from=now-2y&to=now) to a range outside the locked boundaries and refresh. Check if annotation data from outside the locked range is visible.Affected if Annotations appear outside the configured locked timerange, confirming the vulnerability is present
A user is affected if they run a Grafana version within the affected ranges AND have public dashboards with annotations enabled AND timerange lock configured, where annotation data leaks outside the locked time boundaries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped11.6.1012.1.6
Enable and properly configure the timerange lock feature on public dashboards, and apply any available security patches from Grafana that enforce timerange restrictions on annotation queries.
Upgrade to 11.6.10 (for 9.3.x-11.6.x), 12.1.6 (for 12.0.x-12.1.x), 12.2.5 (for 12.2.x), or 12.3.3 (for 12.3.x)
- 1. Identify the current Grafana version by checking the grafana-server version or /api/health endpoint
- 2. Based on the current version, upgrade to the appropriate fixed release: For 9.3.x-11.6.x, upgrade to 11.6.10; For 12.0.x-12.1.x, upgrade to 12.1.6; For 12.2.x, upgrade to 12.2.5; For 12.3.x, upgrade to 12.3.3
- 3. Review the Grafana upgrade guide for your deployment method (Docker, Kubernetes, package manager, or binary)
- 4. Perform the upgrade following standard Grafana upgrade procedures
- 5. After upgrade, verify that public dashboards correctly restrict annotations to the locked timerange
- 6. Test that existing public dashboards with annotations still function as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Grafana
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21722 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data