dbcve.org
GrafanaApplication

CVE-2026-33382

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 11.6.15 / 12.2.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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
Several Grafana API endpoints, some of them unauthenticated, do not limit the size of the request body before processing it. An attacker can send very large payloads that force excessive memory allocation, potentially exhausting memory and 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 API endpoints lack request body size limits, allowing unauthenticated attackers to send large payloads that force excessive memory allocation, leading to memory exhaustion and denial of service.

MitigationImplement request body size limits on all Grafana API endpoints, particularly unauthenticated ones, and configure appropriate memory thresholds to reject oversized requests before processing.

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.15>= 12.2.0, < 12.2.9>= 12.3.0, < 12.3.7>= 12.4.0, < 12.4.4>= 13.0.0, < 13.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 --version` or check the Grafana UI footer, or inspect the grafana-server binary metadata
    Affected if The installed version falls within >= 11.6.0, < 11.6.15; >= 12.2.0, < 12.2.9; >= 12.3.0, < 12.3.7; >= 12.4.0, < 12.4.4; >= 13.0.0, < 13.0.2
  2. Confirm unauthenticated API exposure
    Review your reverse proxy or firewall rules to determine whether Grafana API endpoints (such as /api/*) are accessible without authentication
    Affected if Unauthenticated access to Grafana API endpoints is permitted from untrusted networks
  3. Check for body size limit configuration
    Inspect grafana.ini for settings under [server] or [api] sections, specifically looking for any max_body_size, body_size_limit, or similar directives; if using a reverse proxy, also check its configuration for client_max_body_size or equivalent limits
    Affected if No request body size limits are configured on Grafana API endpoints or upstream proxies
  4. Verify memory limits
    Check Grafana startup flags and systemd/service configuration for memory-related flags such as --max-body-size or memory allocation limits
    Affected if No memory thresholds are set to reject oversized requests before they trigger excessive allocation

You are affected if your Grafana version is in the affected ranges AND unauthenticated API endpoints are exposed AND no request body size limits are configured, allowing attackers to exhaust memory with large payloads.

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.15 / 12.2.9 / 12.3.7 or later
Fixed in 11.6.1512.2.912.3.7
Interim mitigation

Implement request body size limits on all Grafana API endpoints, particularly unauthenticated ones, and configure appropriate memory thresholds to reject oversized requests before processing.

Recommended fix High confidence

Upgrade to Grafana 12.4.4 or later (or 11.6.15+, 12.2.9+, 12.3.7+ for respective branches)

  1. 1. Identify the currently running Grafana version using `grafana-cli --version` or the UI: Server > Stats
  2. 2. Review the current Grafana installation method (e.g., docker, apt/yum, binary)
  3. 3. For Docker: Stop the container, pull the fixed image (e.g., `docker pull grafana/grafana:12.4.4`), and restart with the same configuration
  4. 4. For apt-based systems: Run `sudo apt-get update && sudo apt-get install grafana=2:12.4.4`
  5. 5. For yum-based systems: Run `sudo yum update grafana-12.4.4`
  6. 6. For binary installation: Download the appropriate package from grafana.com/grafana/download for version 12.4.4 or later
  7. 7. After upgrade, restart the Grafana service: `sudo systemctl restart grafana-server`
  8. 8. Verify the new version is running and monitor memory usage under load to confirm the fix
Caveat Review Grafana 12.x release notes for breaking changes between your current version and 12.4.x; major version upgrades may require configuration or dashboard migration

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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