dbcve.org
GrafanaApplication

CVE-2026-28375

MEDIUM · 6.5 CVSS v3.1 Developing Published 2026-03-27
Fix available
A fix is available. Upgrade to 8.1.0 / 12.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A testdata data-source can be used to trigger out-of-memory crashes in Grafana.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-30.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 8.1.0 / 12.0.0 / 12.2.0 or later
Fixed in 8.1.012.0.012.2.0
Recommended fix Moderate confidence

Grafana 12.3.0 (or 12.2.8+, 12.1.10+, or 12.0.0+ depending on your starting version)

  1. 1. Identify your current Grafana version using `grafana-cli --version` or the Grafana UI (Configuration > About)
  2. 2. For Grafana 8.x (< 8.1.0): Upgrade to 8.5.x or later (8.x is EOL, consider upgrading to a supported major version)
  3. 3. For Grafana 11.6.x: Upgrade to 12.0.0 or later (note: 12.0.x also has this vulnerability - go to 12.1.10+, 12.2.0+, or 12.3.0+)
  4. 4. For Grafana 12.0.x: Upgrade to 12.1.10 or later
  5. 5. For Grafana 12.1.x: Upgrade to 12.2.0 or later (note: 12.2.0-12.2.7 also has this vulnerability - go to 12.2.8+)
  6. 6. For Grafana 12.2.x: Upgrade to 12.3.0 or later
  7. 7. Verify the upgrade was successful and Grafana starts without out-of-memory errors
  8. 8. If upgrading across major versions (e.g., 8.x to 12.x), review the changelog for breaking changes and migration steps
Caveat Upgrading across major versions (e.g., 8.x to 12.x) may introduce breaking changes; review Grafana upgrade guides and changelogs for plugin compatibility, dashboard JSON changes, and deprecated features

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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