CVE-2026-33382 in Grafana OSS
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.
Quick answer
Grafana OSS should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Grafana OSS 11.6.0 through 11.6.14
- Grafana OSS 12.2.0 through 12.2.8
- Grafana OSS 12.3.0 through 12.3.6
- Grafana OSS 12.4.0 through 12.4.3
- Grafana OSS 13.0.0 through 13.0.1
Fixed versions
- Grafana OSS 11.6.15, 12.2.9, 12.3.7, 12.4.4, or 13.0.2
How to fix it
Update Grafana OSS. The old Grafana build can allow page script issues or memory denial of service.
- Upgrade Grafana to Grafana OSS 11.6.15, 12.2.9, 12.3.7, 12.4.4, or 13.0.2.
- Restart Grafana.
- Review OAuth, dashboards, and API access.
- Watch Grafana memory and error logs after release.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Grafana reports a fixed version.
- Scan again and confirm CVE-2026-33382 is gone.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-33382?
Grafana OSS versions listed as affected should be reviewed: Grafana OSS 11.6.0 through 11.6.14, Grafana OSS 12.2.0 through 12.2.8, Grafana OSS 12.3.0 through 12.3.6, Grafana OSS 12.4.0 through 12.4.3, Grafana OSS 13.0.0 through 13.0.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.