dbcve.org
GrafanaApplication

CVE-2026-28383

MEDIUM · 6.5 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 →
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 request to the Grafana plugin resources endpoint can cause unbounded memory allocation by reading the entire request body into memory. An authenticated user can exploit this to trigger an out-of-memory condition, potentially causing a denial of service.

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

Grafana's plugin resources endpoint lacks proper request body size limits, allowing authenticated users to send arbitrarily large requests. The endpoint reads the entire request body into memory without bounds, enabling an attacker to exhaust server memory and cause a denial of service.

MitigationImplement request body size limits on the plugin resources endpoint and enforce memory allocation constraints to prevent unbounded memory consumption.

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
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 at Settings > About, or inspect the running container/ service version
    Affected if The installed version falls within any of these ranges: 8.5.0 to 11.6.13, 11.6.14, 12.2.0 to 12.2.7, 12.2.8, 12.3.0 to 12.3.5, 12.3.6, 12.4.0 to 12.4.2, 12.4.3, 13.0.0, or 13.0.1
  2. Verify plugin resources endpoint is accessible
    Confirm that Grafana plugins are installed and the plugin resources API endpoint at `/api/plugins/:pluginId/resources/*` is reachable
    Affected if Plugins are installed and the endpoint is exposed without additional authentication layers beyond Grafana's built-in auth
  3. Confirm authentication is enabled
    Check Grafana configuration (grafana.ini) for auth settings and verify that anonymous access is disabled or limited
    Affected if Authenticated users can access the plugin resources endpoint, as the vulnerability requires at least authenticated user access
  4. Check for request body size limits
    Inspect Grafana configuration files and any reverse proxy settings for max request body size, content-length limits, or similar restrictions on the plugin API routes
    Affected if No explicit body size limits are configured on the plugin resources endpoint or at the proxy level

If the Grafana version is in the affected list AND the plugin resources endpoint is accessible to authenticated users without body size limits, the environment is vulnerable to memory exhaustion via oversized requests.

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 request body size limits on the plugin resources endpoint and enforce memory allocation constraints to prevent unbounded memory consumption.

Recommended fix High confidence

Grafana 12.4.3 (or latest 12.x stable)

  1. 1. Identify the currently installed Grafana version using `grafana --version` or the UI status page
  2. 2. Based on the current version, plan upgrade to the appropriate fixed release: if on 8.5.0-11.x upgrade to 11.6.14+, if on 12.2.x upgrade to 12.2.8+, if on 12.3.x upgrade to 12.3.6+, if on 12.4.x upgrade to 12.4.3+
  3. 3. Backup Grafana configuration files (usually in /etc/grafana) and the database
  4. 4. Stop the Grafana service: `systemctl stop grafana-server` or equivalent
  5. 5. Install the updated Grafana package for your distribution (e.g., apt update && apt install grafana for Debian/Ubuntu, or yum update grafana for RHEL/CentOS)
  6. 6. Start the Grafana service: `systemctl start grafana-server`
  7. 7. Verify the upgrade by checking the version in the UI or via CLI
Caveat Major version upgrades (e.g., 11.x to 12.x) may introduce breaking changes; review release notes 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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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