Security readout for executives and security teams
Plain-English summary
An authenticated user of Grafana OSS can send an oversized or streaming request to the Grafana Live push endpoint and force the server to consume all available memory, causing the monitoring platform to crash. This is an availability issue: dashboards, alerts, and observability workflows can be knocked offline until the service is restarted, which matters most for teams that depend on Grafana for real-time operational visibility.
Executive priority
Moderate. This is an availability bug in a monitoring platform, not a data breach risk. Prioritize patching where Grafana is business-critical for incident response, SRE, or customer-facing dashboards; standard patch cycles are acceptable for isolated internal instances with tight account controls.
Technical view
The Grafana Live push endpoint does not bound the size of incoming request bodies, allowing unrestricted resource consumption (CWE-770). An authenticated attacker with access to the Live API can submit a large or streaming payload that triggers unbounded memory allocation, resulting in an out-of-memory condition on the Grafana process. CVSS 3.1 is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H): network-reachable, low complexity, requires low privileges, high availability impact only.
Likely exposure
Any Grafana OSS deployment in the listed version ranges where the Live push endpoint is reachable by authenticated users. Exposure grows when Grafana is internet-facing, when self-service signup is enabled, or when many low-privilege accounts exist. Isolated internal instances behind SSO and network controls face materially lower exposure than shared or public-facing tenants.
Exploitation context
No active exploitation is reported in the source bundle and the CVE is not listed in CISA KEV. Exploitation requires an authenticated Grafana account with access to the Live API, which raises the bar but is trivial where accounts are broadly provisioned. Impact is denial of service to the Grafana instance; there is no confidentiality or integrity impact per the CVSS vector.
Researcher notes
CWE-770 unrestricted resource allocation on the Live push endpoint; CVSS vector confirms availability-only impact with PR:L. The affected list enumerates specific OSS versions across the 8.x through 13.x lines but the source bundle does not name a fixed version — consult the linked Grafana advisory for the authoritative patched release and any configuration mitigation. No KEV listing and no public exploit references in the bundle.
Mitigation direction
- Review the Grafana security advisory and upgrade to a fixed release identified there.
- Restrict access to the Grafana Live push endpoint via network controls or a reverse proxy.
- Enforce request body size limits at the proxy or load balancer in front of Grafana.
- Audit and tighten Grafana account provisioning, disabling anonymous or self-service signup.
- Monitor Grafana process memory and set OOM restart policies to reduce outage duration.
Validation and detection
- Inventory Grafana OSS instances and compare running versions against the affected list in the advisory.
- Confirm whether the Grafana Live push endpoint is reachable from untrusted networks or shared tenants.
- Enumerate accounts with Live API access and validate least-privilege alignment.
- Test upstream proxy body-size limits against representative Live payloads in a non-production environment.
- After patching, verify the Grafana version and re-check advisory guidance for residual configuration steps.
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-28376 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-28376CVE 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.