Security readout for executives and security teams
Plain-English summary
A flaw in Grafana lets any logged-in user overload the server's memory by sending a specially crafted request to a plugin endpoint. The server tries to load the whole request into memory, which can crash the service and interrupt dashboards and monitoring. Business impact is availability loss for teams that rely on Grafana for observability, not data theft or tampering.
Executive priority
Moderate priority: schedule patching in the next standard maintenance window, sooner if Grafana is exposed to untrusted users or the internet. This is an availability issue for observability tooling; a successful attack disrupts monitoring but does not leak data.
Technical view
The Grafana plugin resources endpoint reads the entire HTTP request body into memory without size limits, enabling CWE-770 uncontrolled resource consumption. An authenticated attacker (PR:L) can submit oversized requests to force an out-of-memory condition and denial of service. CVSS 3.1 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Grafana's advisory lists specific fixed versions across the 11.x through 13.x branches.
Likely exposure
Any Grafana OSS deployment on the affected version lines where users can authenticate and reach plugin resource endpoints is exposed. Internet-facing or multi-tenant Grafana instances face higher risk; instances behind SSO with tightly scoped, trusted users face lower practical risk but remain vulnerable to insider or credential-compromise scenarios.
Exploitation context
Not listed in CISA KEV and no public reports of active exploitation are cited in the source bundle. Exploitation requires valid authentication, which lowers opportunistic risk but keeps the issue relevant where accounts are broadly provisioned or credentials can be phished. No exploit code is referenced in the provided sources.
Researcher notes
CWE-770 uncontrolled resource allocation via unbounded request-body read in the plugin resources handler. Authentication is required (PR:L) but no user interaction. Confirm exact fixed versions from the Grafana advisory before rollout, since the affected list spans multiple release branches (11.x, 12.x, 13.x). Consider request-size caps at the reverse proxy as compensating control until patching completes.
Mitigation direction
- Upgrade Grafana OSS to a fixed release identified in the vendor advisory for your branch.
- Restrict Grafana access to trusted networks or SSO-authenticated users only.
- Enforce least-privilege on Grafana accounts and disable unused plugin functionality.
- Place Grafana behind a reverse proxy that caps request body size.
- Monitor Grafana process memory and enable automatic restart on OOM.
Validation and detection
- Inventory Grafana instances and record installed version against the vendor advisory list.
- Confirm patched build is deployed by checking the Grafana version banner and API version endpoint.
- Review authentication configuration and identify who can reach plugin resource endpoints.
- Test upstream request-size limits on any reverse proxy fronting Grafana.
- Audit logs for unusually large plugin resource requests or repeated OOM restarts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-28383 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6GRAFANAVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://grafana.com/security/security-advisories/cve-2026-28383CVE reference, GRAFANA · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.