dbcve.org
GrafanaApplication

CVE-2026-33375

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 11.6.14 / 12.1.10 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
The Grafana MSSQL data source plugin contains a logic flaw that allows a low-privileged user (Viewer) to bypass API restrictions and trigger a catastrophic Out-Of-Memory (OOM) memory exhaustion, crashing the host container.

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

The Grafana MSSQL data source plugin has a logic flaw that permits low-privileged Viewer users to circumvent API access controls and trigger uncontrolled memory consumption, leading to container-level Out-Of-Memory crashes.

MitigationRestrict the Viewer role from accessing the MSSQL data source plugin configuration or upgrade to a patched version that enforces proper permission boundaries and implements memory consumption limits.

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:>= 11.6.0, < 11.6.14>= 12.1.0, < 12.1.10>= 12.2.0, < 12.2.8>= 12.3.0, < 12.3.6>= 12.4.0, < 12.4.2

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

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 -v' or check the Grafana admin UI under 'Help > About' to obtain the exact version number
    Affected if The installed version falls within any of these ranges: 11.6.0 to 11.6.14, 12.1.0 to 12.1.10, 12.2.0 to 12.2.8, 12.3.0 to 12.3.6, or 12.4.0 to 12.4.2
  2. Verify MSSQL data source plugin is present
    Check the Grafana plugins directory or list installed data sources via the API endpoint '/api/plugins' or through the UI at 'Connections > Data sources'
    Affected if The MSSQL data source plugin is installed and enabled in the Grafana instance
  3. Confirm Viewer role has MSSQL access
    Review role permissions in Grafana under 'Administration > Users and access > Roles' or check the data source permissions settings at 'Configuration > Data sources > [MSSQL] > Permissions'
    Affected if Viewer users or the Viewer role is granted permission to query or access the MSSQL data source
  4. Check for OOM crash indicators
    Review container or system logs for Out-Of-Memory errors occurring around the time of Viewer-initiated MSSQL queries, or check Grafana logs for memory exhaustion events
    Affected if Grafana has experienced unexplained OOM crashes or memory spikes when MSSQL data sources are queried

You are affected if your Grafana version is within the vulnerable ranges AND the MSSQL data source plugin is accessible to Viewer role users, which could enable them to trigger memory exhaustion.

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.1.10 / 12.2.8 or later
Fixed in 11.6.1412.1.1012.2.8
Interim mitigation

Restrict the Viewer role from accessing the MSSQL data source plugin configuration or upgrade to a patched version that enforces proper permission boundaries and implements memory consumption limits.

Recommended fix High confidence

Upgrade to Grafana 11.6.14+, 12.1.10+, 12.2.8+, or 12.3.6+ (depending on your current major version)

  1. Identify the currently installed Grafana version using `grafana-cli --version` or checking the Grafana UI/API
  2. If running 11.6.x, upgrade to version 11.6.14 or later
  3. If running 12.1.x, upgrade to version 12.1.10 or later
  4. If running 12.2.x, upgrade to version 12.2.8 or later
  5. If running 12.3.x, upgrade to version 12.3.6 or later
  6. After upgrade, restart the Grafana service to apply changes
  7. Verify the upgrade was successful and the MSSQL plugin is functioning correctly
Caveat Review Grafana release notes for breaking changes between your current version and the target upgrade version before proceeding

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-33375 — 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-33375 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