dbcve.org
GrafanaApplication

CVE-2026-27877

HIGH · 7.5 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 9.3.0 / 12.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards. No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-sources as far as possible to improve your deployments' security.

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 confidence

In affected deployments, public dashboards expose credentials for all direct (non-proxied) data-sources, even when those data-sources aren't used in any dashboard. Only proxied data-sources properly protect their credentials from exposure through public dashboard access.

MitigationConvert all direct data-sources to proxied data-sources to prevent credential exposure via public dashboards. This architectural change ensures passwords are not transmitted directly to client browsers.

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:< 9.3.0>= 11.6.14, < 12.0.0>= 12.1.10, < 12.2.0>= 12.2.8, < 12.3.0>= 12.3.6, < 12.4.0

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

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

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

  1. Check Grafana version
    Run `grafana-server -v` or check the /api/health endpoint, or look in the installation directory for version file
    Affected if Version is < 9.3.0 OR between 11.6.14-12.0.0 OR between 12.1.10-12.2.0 OR between 12.2.8-12.3.0 OR between 12.3.6-12.4.0
  2. Verify public dashboards are enabled
    Check grafana.ini for `[public_dashboards]` section and `enabled = true`, or query API: GET /api/health
    Affected if Public dashboards feature is enabled in configuration
  3. List configured data sources
    Query API: GET /api/datasources (requires admin auth) or inspect grafana.db sqlite database in data directory
    Affected if Any data source exists with type set to direct (not proxied)
  4. Check data source configuration type
    Examine each data source JSON - look for `"accessMode": "direct"` or equivalent in data source settings via API GET /api/datasources/{id}
    Affected if Any data source has accessMode set to direct rather than proxy
  5. Test public dashboard API response
    Access a public dashboard URL, then inspect browser network traffic or use API tools to capture the response from the public dashboard endpoint
    Affected if API response includes password or secureJsonData fields for data sources not used in that specific dashboard

User is affected if running a vulnerable Grafana version AND has public dashboards enabled AND has at least one direct data source configured, with password exposure confirmed in public dashboard API responses.

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 9.3.0 / 12.0.0 / 12.2.0 or later
Fixed in 9.3.012.0.012.2.0
Interim mitigation

Convert all direct data-sources to proxied data-sources to prevent credential exposure via public dashboards. This architectural change ensures passwords are not transmitted directly to client browsers.

Recommended fix High confidence

Grafana 12.3.0 or later (latest stable release)

  1. Upgrade to Grafana 9.3.0 or later if currently on version < 9.3.0
  2. Upgrade to Grafana 12.0.0 or later if currently on version 11.6.14 through 11.x
  3. Upgrade to Grafana 12.2.0 or later if currently on version 12.1.10 through 12.1.x
  4. Upgrade to Grafana 12.3.0 or later if currently on version 12.2.8 through 12.2.x
  5. After upgrading, convert direct data-sources to proxied data-sources where possible to further reduce exposure
Caveat Review Grafana upgrade notes for potential breaking changes between major versions; test upgrades in non-production environment first

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27877 — 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-27877 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