dbcve.org
GrafanaApplication

CVE-2026-33377

HIGH · 7.1 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 11.6.14 / 12.2.8 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard. The user must have write access to the dashboard to escalate privilege.

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 · moderate confidence

A user with Editor role and write access to a dashboard can overwrite a dashboard they do not own, allowing them to acquire admin privileges on that specific dashboard. This is a privilege escalation vulnerability stemming from insufficient ownership validation during dashboard modification.

MitigationImplement strict ownership validation to prevent users from modifying dashboards they do not own, and explicitly block privilege escalation for non-owner users regardless of write access permissions.

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
Affected:>= 8.5.0, < 11.6.14>= 12.2.0, < 12.2.8>= 12.3.0, < 12.3.6>= 12.4.0, < 12.4.3= 11.6.14= 12.2.8= 12.3.6= 12.4.3= 13.0.0= 13.0.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana version
    Run 'grafana-server --version' or check the version file typically at /usr/share/grafana/version, or query the Grafana API at /api/health
    Affected if The installed version falls within any of the affected ranges: >= 8.5.0 and < 11.6.14; >= 12.2.0 and < 12.2.8; >= 12.3.0 and < 12.3.6; >= 12.4.0 and < 12.4.3; or equals 11.6.14, 12.2.8, 12.3.6, 12.4.3, 13.0.0, or 13.0.1
  2. Verify Editor role users exist with write access
    Query user permissions via Grafana API at /api/users or inspect organization roles in the Grafana UI under Configuration > Users and Teams
    Affected if Any user possesses the Editor role with write permissions to dashboards they do not own
  3. Review dashboard ownership configuration
    Check dashboard JSON metadata for 'createdBy' and 'updatedBy' fields via API at /api/dashboards/uid/{uid}, or examine dashboard settings in the Grafana UI
    Affected if Dashboards allow modification by users who are not listed as the dashboard owner (createdBy does not match the modifying user)
  4. Confirm dashboard overwrite capability for non-owners
    Attempt to update a dashboard you do not own using the POST /api/dashboards/db endpoint with the dashboard UID, or review API access logs for successful non-owner modifications
    Affected if Users with Editor role can successfully overwrite dashboards they do not own, allowing them to acquire admin privileges on that specific dashboard

You are affected if running a vulnerable Grafana version AND users with Editor role can modify dashboards they do not own, leading to unintended privilege escalation on those dashboards.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.6.14 / 12.2.8 / 12.3.6 or later
Fixed in 11.6.1412.2.812.3.6
Interim mitigation

Implement strict ownership validation to prevent users from modifying dashboards they do not own, and explicitly block privilege escalation for non-owner users regardless of write access permissions.

Recommended fix High confidence

11.6.14 (for 8.5.0-11.x), 12.2.8 (for 12.2.x), 12.3.6 (for 12.3.x), or 12.4.3 (for 12.4.x)

  1. 1. Identify the current Grafana version by checking the Grafana UI (Settings > About) or running `grafana-server --version`
  2. 2. Determine which version branch your current installation is on (8.x, 11.x, 12.2.x, 12.3.x, or 12.4.x)
  3. 3. For Grafana 8.5.0 - 11.x: Upgrade to version 11.6.14 or later
  4. 4. For Grafana 12.2.x: Upgrade to version 12.2.8 or later
  5. 5. For Grafana 12.3.x: Upgrade to version 12.3.6 or later
  6. 6. For Grafana 12.4.x: Upgrade to version 12.4.3 or later
  7. 7. Backup the Grafana database and configuration files before upgrading
  8. 8. Perform the upgrade using your package manager or by downloading the appropriate package from grafana.com
Caveat Grafana minor and major version upgrades may introduce breaking changes; review the release notes for your target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33377 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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